documentation-maintenance

Verify each documentation file against the actual code before editing, then update or remove stale claims rather than adding caveats for old behavior. This Skill covers README, GUIDE, TESTING, AGENTS, Copilot instructions, and local skill files after any code, route, config, or build change.

Update README.md for route overviews, GUIDE.md for architecture and route ownership, and TESTING.md if validation commands change. Admin user routes must stay documented under /users, never /auth/users.

Run it after changes affecting API or Web behavior, routes, response contracts, environment variables, Docker Compose, package scripts, CSS architecture, test commands, or reusable project conventions.

No, it only edits documentation and agent guidance files such as README, GUIDE, TESTING, AGENTS, Copilot instructions, skill files, and prompt files. It verifies documentation against code but does not change implementation.

CSS guidance must remain mobile-first and use only the allowed breakpoints 640, 768, 1024, 1280, and 1536. Documentation describing other breakpoints or desktop-first patterns should be corrected or removed.