subagents-orchestration-guide
Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.
documentation-criteria
Documentation creation criteria including PRD, ADR, Design Doc, and Work Plan requirements with templates. Use when creating or reviewing technical documents, or determining which documents are required.
ai-development-guide
Technical decision criteria, anti-pattern detection, debugging techniques, and quality check workflow. Use when making technical decisions, detecting code smells, or performing quality assurance.
coding-principles
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
external-resource-context
Captures and persists access methods for resources outside the repository (design source, design system, API schema, IaC source, secret store) so downstream work can reach them deterministically. Use when work depends on external resources, or when the user mentions design source, design system, API schema, IaC source, secret store, or canonical source.
implementation-approach
Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
integration-e2e-testing
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.
llm-friendly-context
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream agents can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
recipe-add-integration-tests
Add integration/E2E tests to existing codebase using Design Docs
recipe-build
Execute decomposed tasks in autonomous execution mode
recipe-design
Execute from codebase analysis to design document creation
recipe-diagnose
Investigate problem, verify findings, and derive solutions
recipe-front-adjust
Adjust an already-implemented UI in-session with verification against the design source
recipe-front-build
Execute frontend implementation in autonomous execution mode
recipe-front-design
Execute from codebase analysis to frontend design document creation
recipe-front-plan
Create frontend work plan from design document and obtain plan approval
recipe-front-review
Design Doc compliance and security validation with optional auto-fixes
recipe-fullstack-build
Execute decomposed fullstack tasks with layer-aware agent routing
recipe-fullstack-implement
Orchestrate full-cycle implementation across backend and frontend layers
recipe-implement
Orchestrate the complete implementation lifecycle from requirements to deployment
recipe-plan
Create work plan from design document and obtain plan approval
recipe-prepare-implementation
Verifies the work plan is implementable end-to-end and resolves verification-lane / fixture / E2E-environment gaps before the build phase begins. Use when "implement-ready/verification readiness/lane setup/E2E environment missing" is mentioned, or before any build phase begins on a work plan whose readiness has not been preflight-checked.
recipe-reverse-engineer
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
recipe-review
Design Doc compliance and security validation with optional auto-fixes
recipe-task
Execute tasks following appropriate rules with rule-advisor metacognition
recipe-update-doc
Update existing design documents (Design Doc / PRD / ADR) with review
task-analyzer
Performs metacognitive task analysis and skill selection. Use when determining task complexity, selecting appropriate skills, or estimating work scale.
test-implement
Test implementation patterns and conventions. Use when implementing unit tests, integration tests, or E2E tests, including RTL+Vitest+MSW component testing and Playwright E2E testing.
testing-principles
Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.
typescript-rules
React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.
mcp-local-rag
Search, ingest, expand chunk context, or manage local documents via a local RAG MCP server (tools: query_documents, read_chunk_neighbors, ingest_file, ingest_data, delete_file, list_files). Use when user says "search my docs", "save this page", "read around that chunk", "what did I save about X", or invokes `npx mcp-local-rag`.
documentation-criteria
Guides PRD, ADR, Design Doc, UI Spec, and Work Plan creation. Use when creating or reviewing technical documents, or when "UI spec/screen design/component decomposition" is mentioned.
coding-standards
Detects code smells, anti-patterns, and readability issues. Use when implementing features, reviewing code, or refactoring.
frontend-technical-spec
Defines frontend environment variables, component design, and data flow patterns. Use when configuring React environment.
frontend-typescript-rules
Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React components.
frontend-typescript-testing
Designs tests with React Testing Library, MSW, and Playwright E2E. Applies component testing and E2E testing patterns.
implementation-approach
Selects implementation strategy (vertical slice, horizontal, or hybrid) with risk assessment. Use when planning feature implementation.
integration-e2e-testing
Designs integration and E2E tests with mock boundaries and behavior verification rules. Use when writing E2E or integration tests.
llm-friendly-context
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream agents can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
project-context
Provides project-specific prerequisites for AI execution accuracy — domain constraints, development phase, directory conventions, external resource access methods. Use when the session starts, when checking project structure, or when a task references domain rules or external resources outside the repository.
skill-optimization
Evaluates and optimizes skill file quality using 8 content patterns and 9 editing principles. Use when creating skills, refining skill content, or auditing skill quality.
subagents-orchestration-guide
Coordinates subagent task distribution and collaboration. Controls scale determination and autonomous execution mode.
task-analyzer
Analyzes task essence and selects appropriate skills. Returns scale estimates and metadata. Use when starting tasks or selecting skills.
technical-spec
Defines environment variables, architecture design, and build/test commands. Use when configuring environment or designing architecture.
typescript-rules
Applies type safety and error handling rules. Enforces no-any policy and type guards. Use when implementing TypeScript or reviewing types.
typescript-testing
Applies Vitest test design and quality standards. Provides coverage requirements and mock usage guides. Use when writing unit tests.