Reflecting — Update Project Documentation
After completing significant features or structural changes, review and update all project documentation.
Steps
- •
Read current state of all docs and source files:
- •
README.md,CLAUDE.md,AGENTS.md - •
wrangler.jsonc,src/worker.js(scan routes),public/index.html(scan version + features) - •All files in
.claude/skills/
- •
- •
Check README.md:
- •Features list matches what's implemented
- •Project structure matches actual file tree
- •Environment variables table is complete
- •API endpoints table is complete
- •Setup instructions are accurate
- •No references to deleted files or old architecture
- •
Check CLAUDE.md:
- •Quick Commands section is current
- •Architecture section matches actual structure
- •API Routes table matches
src/worker.js - •Environment variables table is complete
- •Common Gotchas section covers new patterns
- •External APIs section is current
- •
Check AGENTS.md:
- •Code conventions match current patterns
- •Feature-adding instructions are accurate
- •Any new patterns or conventions documented
- •
Check skills in
.claude/skills/:- •Frontend skill: UI patterns, color scheme, element caching still accurate
- •Backend skill: routing pattern, helper imports, caching still accurate
- •This skill: checklist still complete
- •
Check version: Ensure
<meta name="app-version">was bumped if index.html changed - •
Cross-check consistency: Ensure these are in sync across all docs:
- •API routes table (README.md, CLAUDE.md, backend skill)
- •Environment variables table (README.md, CLAUDE.md)
- •Project structure / file tree (README.md, CLAUDE.md)
- •iOS 12 constraints (CLAUDE.md, frontend skill)
- •Version bumping instructions (CLAUDE.md, frontend skill)
- •
Apply updates to any files that are out of date
- •
Ask the user if they want to commit and push the documentation updates