Best practices for maintaining a large library of Storyline system simulations

We’re exploring Storyline for building a library of software simulations, including processes that move between multiple systems that share data.

For teams doing this at scale:

• How do you structure simulations for easier maintenance when applications change?
• Do you use screen recordings, screenshots, custom-built interactions, or a hybrid?
• What reusable templates/components have worked well?
• Are you using AI to identify UI changes, update simulations, or reduce maintenance effort?

We’re particularly interested in approaches that remain manageable as the simulation library grows.