project-docs

Document an A/B test with variants, hypothesis, and measurement plan

Show plugin documentation and usage

Update all project documentation (README, ARCHITECTURE, process-notes)

Update ARCHITECTURE.md to document system design and patterns

Review uncommitted code changes for consistency, quality, and maintainability

Review the current plan for consistency, duplicates, and complexity

Document current session progress to process-notes.md

Update README.md to reflect current project state

Reviews uncommitted code changes for consistency with project architecture, code quality, and maintainability. Use after writing code and before committing.

Reviews implementation plans for consistency with project architecture, duplicate code, and unnecessary complexity. Use after creating a plan and before implementation.

Documents A/B tests with variants, hypothesis, measurement plan, and conclusions. Use when the user mentions running an A/B test, comparing two variants, or wanting to measure/test something systematically.

Keeps project ARCHITECTURE.md up-to-date with system design, patterns, and conventions. Use when infrastructure changes, new patterns are established, data models change, or when user explicitly requests /architecture command.

Maintains comprehensive project history in process-notes.md that documents work process, decisions, dead ends, and progress. Use when context window fills up (approaching 60% of token budget), when making key decisions or reaching milestones, or when user explicitly requests /process-notes command.

Keeps project README.md up-to-date with current state of the project. Use when structural changes occur, behavior changes, setup/config changes, feature additions/removals, or when user explicitly requests /readme command.