What problem does it solve? Cross-package backend changes in a Go CMS often blur ownership boundaries, duplicate registration glue, and break persistence direction. This Skill provides a disciplined workflow for implementing reusable architecture changes without over-abstracting or reconstructing the whole repository. ## Core Features & Use Cases - Ownership Classification: Assigns behavior to kernel, module, connector/adapter, or project/internal owners and scopes state to application, profile, site, module, or request lifetime. - Declarative Project Rule: Moves generic registration, validation, ordering, and lifecycle mechanics into reusable owners so project code holds only unique identity and bindings. - Persistence Direction Enforcement: Preserves the flow from project selection through connector, module adapter, and repository to service/runtime. - Use Case: When adding a new module with routes, migrations, and seeds, use this Skill to decide which code belongs in the module versus reusable registries, then run focused tests before broad backend checks. ## Quick Start Use the go-cms-development skill to plan and implement a new backend module with routes, migrations, and seeds following the ownership and lifecycle rules.
