
✧t̰̋̃ĥ̤̊ẹ̃̆ s̶̰̋̃p̶̤̂̊ï̶̥̈̃c̶̰̋̊ë̶̤̂̃ c̥̋̃ö̰̂̊ḋ̤̈̃ë̥̋̊ m̰̂̃ṳ̈̋̊s̥̈̃ṫ̰̋̂ f̤̃̊l̥̋̂ö̰̃̊ẅ̤̋✧
Most Used Tags
After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.
Enhance your coding accuracy by handling dependencies effectively before implementation.
Merge competing design documents into a single source of truth.
Enhance response accuracy with self-verification using Chain-of-Verification (CoVe) prompting.
Guidelines describing how to test the code. Use whenever writing new or updating existing code, for example after implementing a new feature or fixing a bug.
Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
Independent code reviewer with no authorship attachment. Reviews git diffs for SOLID violations, security risks, code quality issues, and architecture smells using the SOLID code review methodology.
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
Independent design document reviewer ensuring technical soundness and completeness.
Review design and implementation docs produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.
Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/wip/.
Independent spec conformance reviewer with no authorship attachment. Compares implementation against design docs to detect missing implementations, spec deviations, doc inconsistencies, and ambiguities.
Easily sync your local workflow with the latest updates from the upstream template repository.
TRIGGER when: user asks to work on, implement, or continue tasks from docs/wip (e.g. "work on task 1", "do the next task", "implement first task for X"). Executes written implementation plans with review checkpoints. Use when you have a fully-formed implementation plan to execute in a separate session.