shinpr/claude-code-workflows

AI Developer Guide applies decision criteria, anti-pattern detection, debugging, and quality gates for backend or language-agnostic implementation reviews. Use it to assess code smells, failures, completeness, and fallback behavior.

Coding Principles provides language-agnostic guidance for writing maintainable, readable, and well-structured code. Use it when implementing features, refactoring, or reviewing code quality.

Documentation Criteria determines whether a change needs a PRD, ADR, UI Spec, Design Doc, or Work Plan, and where each belongs. Use it when planning or reviewing technical documentation scope.

External Resource Context records where external resources live and how to reach them for design, implementation, and verification. Use it when work depends on a design source, API schema, IaC source, secret store, or other canonical external system.

Front Adjust adjusts an existing UI in session and verifies the changes against the design source. Use it for targeted frontend updates that need iterative edit-check-refine review.

Front Review validates React and TypeScript frontend changes against a Design Doc and security requirements. Use it after implementation to review compliance, resolve findings, and apply optional fixes.

Frontend AI Guide applies React and TypeScript review criteria to component, hook, and browser-behavior changes. Use it to check implementation completeness, anti-patterns, and frontend quality gates.

Frontend Build Recipe executes materialized frontend task files in autonomous mode. It is used when a work plan has been broken into task files and the orchestrator should run, verify, and clean them up.

Frontend Design Workflow coordinates repository evidence, UI analysis, and optional ADR decisions to produce and approve a frontend design doc. Use it when a frontend change needs scoped requirements and documented design decisions.

Frontend Planning creates a work plan from a design document and routes it through test skeleton generation and review. Use it when frontend work needs approved scope, tasks, and completion criteria before implementation.

Fullstack Build Workflow executes materialized fullstack task files with layer-aware agent routing and a four-step task cycle. It is used to route backend and frontend tasks, run quality fixes, and complete cleanup and reporting.

Fullstack Implementation Orchestrator manages requirements, design, planning, implementation, and QA across backend and frontend layers. It is used for coordinated full-cycle feature work with subagent-driven handoffs and review gates.

Implementation Approach helps choose an implementation strategy by analyzing the current state, comparing options, and defining verification criteria. Use it when planning a change, selecting an approach, or checking constraints and risks.

Integration E2E Testing defines principles for designing integration and end-to-end tests, including ROI scoring, budget limits, and review criteria. Use it when selecting test candidates or checking test quality for UI and service flows.

Integration Test Recipes adds integration and end-to-end tests to an existing codebase using design docs and confirmed requirements. Use it when you need test coverage for backend, frontend, or full-stack behavior.

LLM-Friendly Context helps you write prompts, handoffs, and generated instructions with explicit inputs, outputs, success criteria, and unresolved decisions. Use it when revising LLM-facing artifacts so downstream consumers can act without guessing.

Recipe Build executes materialized task files in autonomous mode. Use it when a work plan has already been turned into task files and the agent should carry them through execution, verification, and cleanup.

Recipe Design coordinates repository-scoped analysis, optional ADR decisions, and Design Doc approval for Medium or Large work. Use it when turning confirmed requirements into an implementation design with review resolution.

Recipe Diagnose investigates a reported problem, verifies findings, and derives likely fixes. Use it for diagnosis flows that need evidence collection, coverage checks, and solution synthesis.

Recipe Implement orchestrates the full implementation lifecycle from requirements analysis through design, planning, implementation, quality assurance, and deployment. Use it when you need to manage multi-step delivery work with subagents and review gates.

Recipe Plan creates a work plan from a design document and guides it through review and approval. Use it when planning implementation work that needs test skeletons and a reviewed plan.

Recipe Reverse Engineer generates PRDs and design docs from an existing codebase by discovering functional scope, then verifying and reviewing each unit before revision. Use it when you need reverse-engineered documentation from code.

Recipe Review validates implementation against a design doc and checks for security issues after changes. It is used when post-implementation review needs compliance checks and optional fix routing.

Recipe Task executes work by selecting rules with rule-advisor and following a dependency-ordered sequence. Use it when a task needs metacognitive analysis, subagent coordination, and rule-based execution.

Recipe Update Doc updates existing design documents, PRDs, or ADRs after review. It is used when a document needs targeted changes and a final approval step.