vadimvitvickiy

Use when a decision, correction, or design rationale emerges that would otherwise be lost when the session ends.

Use when writing a commit message, opening a pull request, titling and describing a change for someone else to review, or deciding how to…

Use when a test fails, a bug is reported, or observed behavior does not match expectation, and before proposing or applying any fix.

Use when starting work in an unfamiliar repository, when locating code across many files, or when a project's code map or architecture…

Use when writing a constructor or initialiser, when a type needs a collaborator to do its work, or when adding a parameter so something…

Use when a change is expected to span multiple files or modules, or when deciding whether to hand work to subagents, run them in parallel…

Use when reading a diff or pull request for defects, when acting as the reviewer on a change you did not write, or when review feedback…

Use when deciding what to build, run, or test after a change, and before claiming that work is complete, fixed, or passing.

Use when authoring or editing a skill, agent, command or hook for this kit, or when deciding whether a piece of guidance belongs in a…

Use when writing or reviewing comments and doc comments, or when a diff adds explanatory prose alongside code.

Use when adding or reviewing log statements, or when deciding what level a message belongs at.

Use when creating or editing a CLAUDE.md or AGENTS.md, when it has grown long, or when a rule in it also exists in an installed skill.