sync-context

Update context files to reflect the current state of the codebase.

Step 1 — Gather what changed

git diff HEAD
git log --oneline -10
git diff HEAD --name-only | grep -E '\.(tsx|ts)$'

Step 2 — Classify each change and route to the correct file

Step 3 — For each update, evaluate

• Is this new or already documented? (Don't duplicate)
• Is the "why" non-obvious? (Only document if a future engineer might undo without understanding)
• Is existing documentation still accurate? (Update or remove stale entries)
• Is this a permanent pattern or temporary workaround? (Only document permanent)

Step 4 — Apply updates

Read the target file, then edit it following the existing format:

• Component catalog: add/update row in the table
• Rules: add section or update existing content
• Anti-patterns: add - bullet item
• Design decisions: add ## section with rationale

Step 5 — Verify

• Root CLAUDE.md must stay under 100 lines
• No duplicate information across files
• All updated files have correct content

What NOT to add

• Implementation details that belong in code comments
• Tutorials or guides
• Obvious decisions that don't need rationale
• Bug workarounds or version-specific notes
• Anything derivable from reading the code directly