What problem does it solve? Static seed content in an app evolves over time, and naive updates can break database references or wipe user state like favorites, completion flags, and soft-delete status. This Skill defines conventions for versioning seed JSON files so content updates ship safely. ## Core Features & Use Cases - Version index management: Maintain a version.json index tracking _latest_seed_version, release dates, file lists, and migration notes for each seed version. - Safe migration strategies: Apply upsert-by-slug migrations for new items, soft deletes (activo = false) for removed items, and coordinated Room schema migrations for structural changes. - User data preservation: Never overwrite user-controlled fields (activo, favorito, completado, visto) when applying new seed versions. - Use Case: When adding six new exercises and revised copy to an Android app's bundled content, create seed v2, document it in version.json, and migrate via upsert while keeping each user's favorites and progress intact. ## Quick Start Ask the assistant to create a new seed version for the updated ejercicios.json file following the content versioning conventions, including the version.json entry and migration notes.
