What problem does it solve? Code changes often leave documentation stale, causing onboarding friction and misleading contributors. This Skill keeps README, GETTING-STARTED, and docs/ pages synchronized with actual behavior whenever features, Sanity setup, routes, environment variables, or workflows change. ## Core Features & Use Cases - Trigger-based scope detection: Maps changed files (middleware, Sanity schema, plopfile, env config) to the exact docs that need updates. - Surgical edit rules: Prefers targeted updates over rewrites, keeps root README concise, and routes detail into docs/features/ and docs/sanity/. - Onboarding sync: Keeps GETTING-STARTED.md aligned with the real first-run path including setup wizard, seed import, and scaffolding commands. - Use Case: After modifying src/middleware.ts basic-auth behavior, the Skill directs you to update docs/features/basic-auth.md and verify related links in docs/README.md. ## Quick Start Ask the assistant to apply the docs-maintenance skill after changing a feature, Sanity schema, or setup script so all affected documentation is updated in the same task.
