arndvs

architect

Comprehensive implementation planning with vertical slices. Use when asked to 'act as an Architect', 'plan this', 'create an implementation plan', 'slice this into tasks', or when a task needs decomposition before execution.

atomic-commits

Atomic commits on a feature branch with conventional messages — Commit mode for checkpoints, Ship mode for PR. Use when committing, checkpointing, shipping, pushing, or creating a PR.

Code & Development Listed

code-review

Focused review of staged or recent changes to find edge cases, logic errors, and integration risks before merging. Use when asked to 'do a code review', 'review my changes', 'review this PR', 'check my diff', 'review staged changes', or 'pre-merge review'.

codebase-audit

Ruthless codebase audit reporting only real problems. Use when asked to 'audit', 'code audit', 'codebase audit', 'review code', 'find bugs', or 'code review'.

do-work

Core execution loop for implementing tasks. Use when asked to 'do work', 'implement', 'build this', 'fix this', 'plan execute clear', 'plan then execute', 'work loop', or when working through a plan or backlog item.

document

Write, update, or audit documentation. Use when asked to 'document this', 'write docs', 'update the README', 'add JSDoc', 'write a changelog', or 'create an ADR'.

error-audit

Use when repeated Claude Code session errors need analysis; scans session transcripts for errors, clusters by root cause, and suggests remediations.

explore

Deep codebase exploration using parallel subagents. Use when asked to 'explore', 'understand', 'investigate', 'map out', 'how does X work', or 'audit' a part of the codebase.

Web & Frontend Listed

frontend-component-style

Frontend component file structure, naming, and layer separation for new or refactored components.

grill-with-docs

Use when stress-testing a plan against the project's domain model — grills the design, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.

halbert-copy-editor

Edit and punch up sales copy, marketing emails, landing pages, ads, and any persuasive writing using the Halbert Copywriting Method.

npm-security-audit

Layered security audit on npm/pnpm/yarn projects before installing or running. Use to vet a GitHub repo, npm package, or local project before npm install/start/npx.

plan-archive

Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.

pr-preflight

Exhaustive pre-PR audit that front-runs code review tools by catching the same issues Copilot/reviewers find iteratively, across any stack.

prd-to-issues

Break a PRD into independently grabbable GitHub issues with dependency relationships. Use when asked to 'break this PRD into issues', 'create issues from PRD', 'plan the work', 'create a kanban', or after writing a PRD to prepare work for execution.

press1-check

Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.

research

Cache expensive exploration into a research document before building. Use when asked to 'research', 'investigate before building', 'gather context', 'flush unknowns', or before a large feature where unknowns need flushing.

review-pr-copilot

Address GitHub Copilot review comments on the active PR by triaging into confidence tiers, fixing in atomic commits, resolving threads, and re-requesting review.

sanity-best-practices

Sanity development best practices — schemas, GROQ, TypeGen, Visual Editing, Functions, Blueprints, and framework integrations. Use when working with Sanity content, schemas, queries, or Studio.

session-close

Pre-flight checklist that runs quality gates before ending a coding session.

sketch-the-solution

7-phase UX design process from user stories to tested interfaces. Use when asked to 'sketch the solution', 'design UX', 'UX process', 'product design process', or when going from idea to interface design.

skill-scaffolder

Meta-skill for creating new agent skills that involve multi-step automation, browser navigation, state tracking, evidence capture, and both local (VS Code Insiders) and VPS (Playwright) execution. Use when the user wants to 'create a skill', 'build a new skill', 'scaffold a skill', 'make a skill for X', or describes a multi-step agentic workflow they want to automate.

stress-test

Invoke to run the adversarial stress test protocol against ctrl+shft rule compliance. Guides a human reviewer through systematic attempts to break rule boundaries — the same methodology a skeptical senior engineer would use before trusting the system in production.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

visual-feedback

Use when implementing UI, checking dark/light mode, or validating animations — adds a visual feedback loop via browser screenshots so frontend changes are verified, not assumed.

write-a-prd

Write a Product Requirements Document from a rough idea. Use when asked to 'write a PRD', 'create a PRD', 'plan a feature', or when starting a new feature that needs scoping.

grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding. Use when asked to 'grill me', 'interview me', 'ask me questions about this', or before writing a PRD to flesh out vague ideas.

improve-architecture

Explore the codebase for architectural improvements using deep module analysis. Use when asked to 'improve architecture', 'improve codebase', 'find shallow modules', 'refactor architecture', or for periodic codebase health checks.

tdd

Red-green refactor workflow for test-driven development. Use when asked to 'write tests first', 'TDD', 'red-green refactor', 'test-driven', or 'failing test first'. Backend-only — do not use for frontend components.