| name | update-claude-documentation |
| description | Update project documentation files (README.md, PROJECT_BRIEF.md, TECH_STACK.md, ARCHITECTURE.md, docs/API.md, docs/DATABASE.md, CLAUDE.md) when significant changes occur. Use for feature additions, architecture changes, dependency updates, API/database modifications. Ensures consistency across all docs. |
Update Claude Documentation
Update project documentation systematically after significant changes. Keep all files consistent and accurate.
Core Principle: Documentation tells one cohesive story. Each file serves a specific audience but must reflect the same reality.
Style Rule: Be precise and concise. Do not add verbose or unnecessary text to any documentation file.
Modularize Instructions (Token Economy): Avoid packing everything into a single CLAUDE.md. Prefer multiple focused docs (e.g., docs/setup.md, docs/api.md, docs/workflows.md) and reference them only when needed to reduce context bloat.
Docs Organization Rule (Required): All documentation markdown now lives under docs/ plus a semantic subdirectory (overview, architecture, pharmacy, localization, etc.). Do not add new files directly to the repo root—move existing root markdown into the appropriate docs/<module> folder before editing, then update docs/agents/AGENTS.md and always update docs/plans/AGENTS.md when plans are added or their status changes. The canonical landing doc is now docs/overview/README.md, and the root README.md should only point people into docs/.
When to Use
✅ Adding/removing features
✅ Architecture or design pattern changes
✅ Dependency or tech stack updates
✅ API endpoints or database schema changes
✅ Project directory restructuring
✅ Development workflow changes
❌ Typo fixes (do directly)
❌ Code comments
❌ WIP features not yet merged
Documentation Files
| File | Audience | Purpose |
|---|
| PROJECT_BRIEF.md | Stakeholders, new devs | 30-sec overview |
| README.md | Developers | Setup, usage guide |
| TECH_STACK.md | Developers, DevOps | Tech inventory |
| ARCHITECTURE.md | Senior devs, architects | System design |
| docs/API.md | API consumers | API reference |
| docs/DATABASE.md | Backend devs, DBAs | Schema docs |
| CLAUDE.md | Claude Code | Dev patterns |
| docs/setup.md | Developers | Setup details |
| docs/api.md | API consumers | API usage guide |
| docs/workflows.md | Developers | Workflow rules |
Change → File Mapping
New Feature:
- README.md (usage)
- docs/API.md (if adds endpoints)
- docs/DATABASE.md (if adds tables)
- ARCHITECTURE.md (if adds components)
- CLAUDE.md (if changes patterns)
- PROJECT_BRIEF.md (if significant)
Tech Stack Change:
- TECH_STACK.md (always)
- README.md (setup instructions)
- ARCHITECTURE.md (if affects design)
- CLAUDE.md (if affects workflows)
Architecture Change:
- ARCHITECTURE.md (always)
- README.md (overview section)
- CLAUDE.md (patterns)
- PROJECT_BRIEF.md (if major)
API/Database Change:
- docs/API.md or docs/DATABASE.md (always)
- ARCHITECTURE.md (if changes contracts)
- CLAUDE.md (if affects patterns)
- README.md (if affects usage)
Update Workflow
1. Understand Change (2-5 min)
Document:
- Type: Feature/Architecture/Tech Stack/API/Database
- What: One sentence description
- Impact: Who/what affected
- Breaking: Yes/No (what breaks)
2. Map to Files (1-2 min)
Order: Specific → General
- Technical Specs (API.md, DATABASE.md)
- Architecture (ARCHITECTURE.md, TECH_STACK.md)
- AI Instructions (CLAUDE.md)
- User Guides (README.md)
- Overview (PROJECT_BRIEF.md)
3. Read Current State (2-3 min)
Read all affected files in parallel.
4. Update Systematically (10-20 min)
Per-file checklist:
5. Verify Consistency (2-3 min)
Check across all files:
6. Final Review (1 min)
Total: 15-30 minutes
Common Mistakes
❌ Updating only one file
# Updated README but forgot CLAUDE.md
# Result: AI doesn't know new pattern
❌ Inconsistent terminology
# README.md: "Authentication Service"
# ARCHITECTURE.md: "Auth Module"
# CLAUDE.md: "Login System"
# Pick ONE term everywhere
❌ Forgetting breaking changes
# Renamed API endpoint but README examples still use old path
# Add migration notes EVERYWHERE affected
❌ General → Specific order
# BAD: Update BRIEF first, then API.md
# GOOD: Update API.md first (precise), then BRIEF (summary)
Quick Reference
Update Order:
API/DB Specs → Architecture → CLAUDE → README → BRIEF
Consistency Checks:
Terminology, Versions, Paths, Names, Features
Time Budget:
Small change: 5-10 min
Medium change: 15-30 min
Major refactor: 45-60 min
Summary
Process: Understand → Map → Read → Update → Verify → Review
Key Rules:
- Update specific docs first, general last
- Read all affected files before editing
- Keep terminology consistent
- Mark breaking changes everywhere
- Test examples before committing
- One reality, multiple perspectives
Remember: Documentation debt compounds fast. Update immediately when making changes.
