Creates and evaluates copy for brand, editorial, product, UX, conversion, and informational surfaces. Use when writing, extracting, editing, syncing, critiquing, or auditing copy. Not for visual identity, page layout, or standalone social bios.
Git workflow for conventional commits, pull request creation, and pull request merging. Use when committing, opening or pushing a pull request, or merging one. Not for code review, acceptance-criteria checks, general branch management, or session wrap-up.
Spec-driven feature work with traceable requirements, design, tasks, audit, and validation. Use when planning, designing, implementing, or validating a feature. Not for unknown-bug diagnosis, standalone product or technical documents, PR or commit mechanics,…
Evidence-led debugging for unexpected, silent, or intermittent failures. Use when tracing bugs, adding targeted logs, or verifying fixes. Not for known one-line fixes, runtime review of deployed services, or PM bug triage.
Clear, precise technical prose that preserves facts, requirements, and terms. Use for explanations, procedures, specifications, documentation, incident reports, and brief factual answers. Not for code-only output, raw logs, compliance certification, or…
Code review in quick and deep modes, with confidence-scored findings. Use for diff review, guideline audits, re-reviewing fixes, or applying findings before a pull request. Not for acceptance-criteria verification, visual design review, or commit and branch…
Claude Code rule management at project and user level. Use when defining conventions, scoping, listing, editing, extracting, or deleting rules. Not for procedural workflows, lifecycle hooks, or one-off task instructions.
Prose editing that removes AI-writing patterns while preserving facts, voice, and format. Use when humanizing or checking a draft for machine-written patterns. Not for authorship detection, source-code changes, fact-checking, translation, or product-copy…