What problem does it solve? Code changes frequently leave documentation stale, causing API references, data models, and deployment guides to drift out of sync with the actual codebase. This Skill enforces a rule that every change to a public contract must update the corresponding doc. ## Core Features & Use Cases - Change-to-Doc Mapping: Directs updates to the correct file in docs/ based on what changed, such as API routes, Prisma models, env vars, workflow steps, or deployment config. - Format Conventions: Standardizes docs with markdown tables, mermaid diagrams, inline code for paths, and changelog date-stamps. - Sync Verification Checklist: Provides a pre-PR checklist confirming endpoints, models, env vars, workflow steps, and user-facing features are documented. - Use Case: After adding a new API endpoint, the Skill walks you through updating docs/api-reference.md with method, path, auth, request/response schemas, and error codes, plus docs/data-model.md if a new model is involved. ## Quick Start Update the project documentation to reflect the new API endpoint and Prisma model I just added.