agent-browser
Browser automation for web testing, form filling, screenshots, and data extraction. Ref-based workflow with best practices for reliable automation.
answer-questions-directly
Ensures questions are answered literally before taking action. Triggers on user input containing '?' or patterns like 'why did you...?', 'will that work?', 'have you considered...?'. Use when user asks about your decisions, challenges an approach, or requests assessment. Prevents interpreting questions as implicit instructions or criticism.
api-design
Build production-ready HTTP APIs with clean handlers, consistent error envelopes, health checks, CORS, and operational excellence.
branch-completion
Use when implementation is complete and tests pass. Guides completion by presenting structured options for merge, PR, or cleanup.
code-flow-analysis
Trace code execution path before implementing fixes. Forces understanding of fn(args, deps) flows, Result types, and workflow composition. Prevents guessing by requiring file:line references and execution diagrams.
code-review-reception
Use when receiving code review feedback, before implementing suggestions. Requires technical verification, not performative agreement or blind implementation.
concise-output
Enforce extreme brevity and high signal-to-noise ratio. Every word must justify its existence. Eliminates verbose explanations, filler phrases, and unnecessary elaboration.
confidence-levels
Force honest confidence assessment. Express confidence as percentage, explain gaps, validate assumptions before presenting conclusions.
config-management
Validate config at startup, secrets in memory only. Never read config during requests, never store secrets in env vars. Use node-env-resolver for multi-source config.
create-tasks
Creates well-formed tasks following a template that engineers can implement. Use when creating tasks, defining work items, creating tasks from PRD, breaking down features, or converting requirements into actionable tasks.
critical-peer
Professional skepticism with pattern enforcement. Verify before agreeing, challenge violations, propose instead of asking. Concise output, research before asking, answer questions literally.
data-visualization
Visualization is communication. Chart selection, encoding hierarchy, accessibility, rendering performance. Use established algorithms - these problems are solved.
debugging-methodology
Evidence-based debugging with Iron Law discipline. Instrument before guessing, trace before theorizing. Use when encountering any bug, test failure, or unexpected behavior - before proposing fixes.
design-exploration
Use before any creative work - creating features, building components, adding functionality. Explores user intent, requirements, and design before implementation. One question at a time, multiple choice preferred.
design-principles
Software design beyond syntax. Fail-fast over fallbacks, explicit over implicit, composition over inheritance. Integrates with fn(args, deps) and Result type patterns. Includes 8-dimension design analysis.
documentation-standards
User-centered documentation quality framework. Eight quality dimensions, document type requirements, and review checklist. Documentation exists to serve readers, not demonstrate knowledge.
fn-args-deps
Enforce the fn(args, deps) pattern: functions over classes with explicit dependency injection
git-worktrees
Use when starting feature work that needs isolation from current workspace. Creates isolated git worktrees with directory selection, safety verification, and baseline testing.
implementation-planning
Use when you have a design or requirements for a multi-step task, before writing code. Creates bite-sized TDD task plans with exact file paths, complete code, and verification steps.
investigation-modes
Three explicit investigation modes: LEARNING (build understanding), INVESTIGATION (diagnose problems), SOLVING (implement fixes). Prefix messages with mode, ask before transitioning.
literal-answers
Treat questions as literal questions. Answer them honestly without interpreting as hidden instructions. STOP after answering - don't immediately act on assumed implications.
observability
Make functions observable with trace() wrapper, structured logging (Pino), and OpenTelemetry. Observability is orthogonal to business logic.
parallel-agent-dispatch
Use when facing 2+ independent tasks that can be worked on without shared state. Dispatch one agent per problem domain for concurrent investigation.
pattern-enforcement
Enforce architectural patterns with ESLint rules. Block infra imports, enforce object params, prevent server/client leaks.
performance-testing
Load testing, chaos engineering, and performance validation. Prove your system works under pressure with k6, trace correlation, and progressive load profiles.
react-development
Modern React architecture patterns and web interface guidelines. Container/View split, framework adapters, React Query, dependency injection, Storybook-first development, accessibility, interactions, animations, performance. User experience over developer convenience.
research-first
Research-driven investigation. Validate solutions and explore documentation before presenting. Never ask questions you can answer yourself through research.
resilience
Add retry, timeout, and circuit breaker patterns at the workflow level. Business functions stay clean.
result-types
Never throw for expected failures. Use Result<T, E> types with explicit error handling and workflow composition.
session-continuity
Persistent task workflow with state machine. Every message MUST announce state. Uses .claude/ files for multi-session continuity. Never use TodoWrite. Never auto-advance tasks.
skill-authoring
Use when creating, editing, or reviewing skills. Covers discovery optimization, structure patterns, testing approaches, and format decisions.
spine-framework
Evaluate and improve technical articles using the SPINE framework. Use when writing blog posts, technical documentation, tutorials, or reviewing draft articles for quality.
storybook-journeys
Create Storybook "user journey" storyboards for React apps (page/screen stories, MSW API mocking, interaction play functions, and optional Storybook test-runner setup). Use when the user wants Storybook demos of flows (not just atomic components), e.g., signup/login/checkout, with mocked APIs and scripted interactions.
strict-typescript
Enforce patterns with TypeScript beyond strict:true. Include noUncheckedIndexedAccess, erasableSyntaxOnly, ts-reset, and type-fest. Advanced type patterns and ESLint enforcement.
structured-writing
Writing assistance with voice preservation. Structure content, ask clarifying questions, identify gaps. Small edits execute; large changes ask first.
system-architecture
Design systems for change. Trade-off analysis, ADR documentation, pattern selection. Architecture decisions must have documented rationale.
tdd-workflow
Strict TDD state machine with Result types. 7-state workflow (PLANNING, RED, GREEN, REFACTOR, VERIFY, BLOCKED, VIOLATION). Every message MUST announce state. Integrates with fn(args, deps), vitest-mock-extended, and typed error handling.
testing-strategy
Test pyramid approach with unit, integration, and load tests. DI enables testability. Use vitest-mock-extended for typed mocks.
ui-design-principles
Design system principles for distinctive, implementation-ready interfaces. Context before design, show don't tell, every state documented.
validation-boundary
Validate at the boundary with Zod schemas and branded types. Business functions trust validated input.
verification-before-completion
Use when about to claim work is complete, fixed, or passing. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.
writing-tests
Principles for writing effective, maintainable tests. Covers naming conventions, assertion best practices, and comprehensive edge case checklists. Based on BugMagnet by Gojko Adzic.