Design Rubric
Use when critiquing, reviewing, or refining visual designs, wireframes, or UI layouts — especially for small/medium SPAs. Applies a six-criterion rubric covering visual clutter, information hierarchy, spacing discipline, data-table rendering, add-flow comprehensibility, and affordance placement. Invoke when the user asks to “review”, “critique”, “audit”, or “refine” a wireframe, mockup, or existi…
Go Performance
>
To Issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Go Style
>
Go Instrumentation
>
Coding Style
>
Codebase Locator
>
Autonomous Orchestration
|
Diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Codebase Analyzer
>
Grill With Docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
To Prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
Go Testing
>
Improve Go Architecture
>
Conventional Commit
Create git commits in Conventional Commits style (type(scope): subject) when the repo's recent history already uses that format; otherwise mirror the repo's existing style. Use when the user asks to commit, says "commit this", "make a commit", "git commit", "stage and commit", or hands over a finished change for committing.