What problem does it solve? Features in this codebase never touch the database directly, so any new data need requires a coordinated change across the repository layer. This Skill ensures all the files that must change together actually do, preventing broken interfaces, untestable SQL, and failing specs. ## Core Features & Use Cases - Coordinated multi-file change: Guides edits to the repository contract interface, the SQLite implementation, the stub used by specs, and the integration spec, plus the row mapper when a new record shape is returned. - Layer discipline enforcement: Keeps SQL confined to one file, enforces UTC datetime handling, transactions for multi-table writes, and domain-named methods that hide table structure. - Use Case: A feature needs the chronology of a game series. Use this Skill to add a seriesChronology method to the interface, implement it in the SQLite repository, register a spy in the stub, and cover it with a real-database integration spec. ## Quick Start Add a repository method for the data my feature needs, following the repository layer workflow.