shinpr/claude-code-workflows

documentation-criteria

Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.

recipe-front-design

Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval

recipe-front-review

Design Doc compliance and security validation with optional auto-fixes

subagents-orchestration-guide

Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.

recipe-design

Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval

recipe-front-design

Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval

recipe-front-review

Design Doc compliance and security validation with optional auto-fixes

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-design

Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval

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

ai-development-guide

Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.

frontend-ai-guide

Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.

implementation-approach

Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.

recipe-diagnose

Investigate problem, verify findings, and derive solutions

recipe-front-build

Execute materialized frontend task files in autonomous execution mode

recipe-front-plan

Create frontend work plan from design document and obtain plan approval

recipe-build

Execute materialized task files in autonomous execution mode

recipe-front-build

Execute materialized frontend task files in autonomous execution mode

recipe-front-plan

Create frontend work plan from design document and obtain plan approval

recipe-fullstack-build

Execute materialized fullstack task files 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-build

Execute materialized task files in autonomous execution mode

recipe-implement

Orchestrate the complete implementation lifecycle from requirements to deployment

recipe-plan

Create work plan from design document and obtain plan approval

recipe-fullstack-build

Execute materialized fullstack task files with layer-aware agent routing

recipe-fullstack-implement

Orchestrate full-cycle implementation across backend and frontend layers

coding-principles

Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.

external-resource-context

Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the user mentions…

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 consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.

requirement-convergence

Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins.

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.

recipe-front-adjust

Adjust an already-implemented UI in-session with verification against the design source

task-analyzer

Selects the smallest set of task-execution skills and metacognitive safeguards for standalone task and diagnosis workflows.

recipe-add-integration-tests

Add integration/E2E tests to existing codebase using Design Docs

recipe-front-adjust

Adjust an already-implemented UI in-session with verification against the design source