docs

Capture wrong assumptions you made about the codebase. TRIGGER when reality differs from expectation (e.g., "assumed Jest but it's Vitest", "assumed AbstractUseCase exists but found AbstractMemberUseCase", "assumed REST but it's GraphQL"). Log silently to .claude/assumption-corrections.yaml to identify CLAUDE.md documentation gaps. Key distinction - assumptions are corrected by reality, decisions are choices between valid options.

Automatically capture reusable task patterns as command candidates after completing coding work. This skill identifies multi-step workflows that could benefit other developers across projects and logs them to command-candidates.yaml for potential automation. Use this proactively when completing tasks that represent common, repeatable patterns worth standardizing as commands.

Capture codebase inconsistencies discovered during exploration OR implementation. TRIGGER when you find conflicting patterns while looking for code to follow (e.g., "some UseCases extend AbstractMemberUseCase, others don't") or different approaches to the same concern across modules (naming, error handling, validation placement). Log silently to .claude/consistency-violations.yaml so teams can standardize later.

Automatically capture implicit technical decisions and uncertainties encountered by AI agents during coding work. This skill logs decision points where the agent chose an approach without explicit user guidance, enabling later review and context enrichment. Use this proactively during any coding task to track "what choices I made and why."