What problem does it solve? Changing an entity that already exists in a live database is risky: a hand-written ALTER, a dropped database, or a migration applied after deployment can break the schema history or take the application down. This Skill enforces the safe Nodefony workflow for evolving a schema and shipping it to production. ## Core Features & Use Cases - Guided schema migration: Evolves the database exclusively through the orm:generate and orm:migrate commands, never through manual ALTER statements or database deletion. - State reading and planning: Reads the current schema state whether or not the application is running, and produces a plan before any change is applied. - Refusal codes and prohibitions: Maps each refusal code to the action it requires, and lists the three forbidden operations that corrupt a migration history. - Deployment pattern: Applies migrations BEFORE application instances during deployment, and covers adopting an existing database and repairing a failed migration. - Use Case: You added a field to an entity and production now reports "no such column". Use this Skill to generate the migration, review the plan, and deploy it before the new code rolls out. ## Quick Start Ask the assistant to migrate the Nodefony schema after adding a field to an entity, so it generates and applies the migration with orm:generate and orm:migrate before deployment.
