Git Workflow
Use for branches, history edits, conflicts, rebases, recovery, force-push, and gh.
Workflow
Use first for every coding task to route risks, choose skills, and define proof.
Debugging
Use to debug failures, reproduce symptoms, isolate causes, inspect evidence, and fix bugs.
Accessibility
Use for accessible UI, WCAG, ARIA, keyboard, focus, contrast, and inclusive states.
Architecture
Use for architecture decisions, module boundaries, coupling, layering, and system shape.
Refactoring
Use for refactoring, behavior-preserving change, tests, and safe rewrites.
Official Source Check
Use when external behavior must be checked against official sources.
Ui Design
Use for frontend UI, layouts, components, responsive behavior, visual design, and usability.
Documentation
Use for requested/approved docs, READMEs, ADRs, runbooks, API docs, comments.
Error Handling
Use for error handling, error types, propagation, retries, user messages, and recovery.
Performance
Use for performance, profiling, latency, throughput, allocation, caching, and hot paths.
Database
Use for databases, schemas, migrations, indexes, transactions, query plans, and locking.
Specify
Use for design-partner mode: discovery, tradeoffs, decisions, and agreed design artifacts.
Security
Use for security, auth, secrets, crypto, input validation, dependency risk, and trust boundaries.
Ship
Run Consult's guarded maintainer flow for commit, merge, version bump, validation, and push.
Contract First
Use when caller-facing interfaces or shared structure need approval before implementation.
Commit
Use for staging reviewed work, commit splits, and messages.
Code Review
Use to review diffs and PRs for bugs, regressions, edge cases, proof, and merge readiness.
Observability
Use for observability, logs, metrics, traces, health checks, dashboards, alerts, and SLOs.
Scaffolding
Use for scaffolding, new projects, package setup, quality tooling, CI, and repo structure.
Api
Use for REST API contracts: endpoints, fields, evolution, status codes, errors, pagination, idempotency.
Async Systems
Use for async systems, concurrency, queues, streams, pub/sub, ordering, and backpressure.
Proof
Use for proof and tests, claims, invariants, behavior specs, edge cases, and evidence.
Domain Modeling
Use for domain modeling, data shapes, invariants, state transitions, parsing, and effects.
Release
Use only on request/approval for release prep, or when validation requires release artifact sync.