What problem does it solve? When an Intent Architect module changes its templates, stereotypes, or folder structure between versions, applications that installed an earlier version keep stale persisted metadata that nothing regenerates automatically. This Skill guides the creation of a Module Migration that programmatically edits the consumer application's own persisted metadata during install or update so it converges onto the shape a fresh install already gets. ## Core Features & Use Cases - Version Migration Elements: Models a Version Migration element under a Module Migrations container, named exactly with the target semver string, and scaffolds an IModuleMigration class via the Software Factory. - Direct Metadata Editing: Uses IPersistenceLoader from Intent.Persistence.SDK to load the consumer application, locate designers, packages, and elements by GUID or name, and remove or restructure stale elements. - Use Case: After flattening a module's File Template folder layout, add a Version Migration that finds the consumer's orphaned old Folder elements in its Codebase Structure designer, removes them and their nested subfolders recursively, and saves the package. ## Quick Start Add a version migration to my module that removes the stale folders left in consumer applications by the previous template layout.
