Build production-ready software with Claude Code - Workflow plugins that bring best practices, specialized agents, and automated quality checks to your development process.
This marketplace includes two plugins:
- dev-workflows - Backend and general-purpose development
- dev-workflows-frontend - React/TypeScript specialized workflows
Choose what fits your project:
# 1. Start Claude Code
claude
# 2. Install the marketplace
/plugin marketplace add shinpr/claude-code-workflows
# 3. Install backend plugin
/plugin install dev-workflows@claude-code-workflows
# 4. Restart session (required)
# Exit and restart Claude Code
# 5. Start building
/implement <your feature># 1-2. Same as above (start Claude Code and add marketplace)
# 3. Install frontend plugin
/plugin install dev-workflows-frontend@claude-code-workflows
# 4-5. Same as above (restart and start building)
# Use frontend-specific commands
/front-design <your feature>Install both plugins to get the complete toolkit for backend and frontend work.
Note: If you encounter SSH errors during installation, see SSH Setup FAQ below.
graph TB
A[π€ User Request] --> B[π requirement-analyzer]
B --> |"π¦ Large (6+ files)"| C[π prd-creator]
B --> |"π¦ Medium (3-5 files)"| D[π technical-designer]
B --> |"π¦ Small (1-2 files)"| E[β‘ Direct Implementation]
C --> D
D --> DR[π document-reviewer]
DR --> DS[π design-sync]
DS --> F[π§ͺ acceptance-test-generator]
F --> G[π work-planner]
G --> H[βοΈ task-decomposer]
H --> I[π¨ task-executor]
E --> I
I --> J[β
quality-fixer]
J --> K[π Ready to Commit]
graph LR
P[π Problem] --> INV[π investigator]
INV --> |Evidence Matrix| ASS{Complex?}
ASS --> |Yes| VER[βοΈ verifier]
ASS --> |No| SOL[π‘ solver]
VER --> |Validated Conclusion| SOL
SOL --> |Solutions + Steps| R[π Report]
graph TB
subgraph Phase1[Phase 1: PRD Generation]
CMD[π /reverse-engineer] --> SD1[π scope-discoverer]
SD1 --> PRD[π prd-creator]
PRD --> CV1[β
code-verifier]
CV1 --> DR1[π document-reviewer]
end
subgraph Phase2[Phase 2: Design Doc Generation]
SD2[π scope-discoverer] --> DD[π technical-designer]
DD --> CV2[β
code-verifier]
CV2 --> DR2[π document-reviewer]
DR2 --> DONE[π Complete]
end
DR1 --> |All PRDs Approved| SD2
- Analysis - Figures out how complex your task is
- Planning - Creates the right docs (PRD, design doc, work plan) based on complexity
- Execution - Specialized agents handle implementation autonomously
- Quality - Runs tests, checks types, fixes errors automatically
- Review - Makes sure everything matches the design
- Done - Clean, production-ready code
| Command | Purpose | When to Use |
|---|---|---|
/implement |
End-to-end feature development | New features, complete workflows |
/task |
Execute single task with precision | Bug fixes, small changes |
/design |
Create design documentation | Architecture planning |
/plan |
Generate work plan from design | Planning phase |
/build |
Execute from existing task plan | Resume implementation |
/review |
Verify code against design docs | Post-implementation check |
/diagnose |
Investigate problems and derive solutions | Bug investigation, root cause analysis |
/reverse-engineer |
Generate PRD/Design Docs from existing code | Legacy system documentation, codebase understanding |
| Command | Purpose | When to Use |
|---|---|---|
/front-design |
Create frontend design docs | React component architecture |
/front-plan |
Generate frontend work plan | Component breakdown planning |
/front-build |
Execute frontend task plan | Resume React implementation |
/task |
Execute single task with precision | Component fixes, small updates |
/review |
Verify code against design docs | Post-implementation check |
/diagnose |
Investigate problems and derive solutions | Bug investigation, root cause analysis |
/reverse-engineer |
Generate PRD/Design Docs from existing code | Legacy system documentation, codebase understanding |
Tip: Both plugins share
/task,/review,/diagnose, and/reverse-engineercommands with the same functionality.
These agents work the same way whether you're building a REST API or a React app:
| Agent | What It Does |
|---|---|
| requirement-analyzer | Figures out how complex your task is and picks the right workflow |
| work-planner | Breaks down design docs into actionable tasks |
| task-decomposer | Splits work into small, commit-ready chunks |
| code-reviewer | Checks your code against design docs to make sure nothing's missing |
| document-reviewer | Reviews single document quality, completeness, and rule compliance |
| design-sync | Verifies consistency across multiple Design Docs and detects conflicts |
| investigator | Collects evidence, enumerates hypotheses, builds evidence matrix for problem diagnosis |
| verifier | Validates investigation results using ACH and Devil's Advocate methods |
| solver | Generates solutions with tradeoff analysis and implementation steps |
| scope-discoverer | Discovers PRD/Design Doc targets from codebase for reverse engineering |
| code-verifier | Validates consistency between documentation and code implementation |
| Agent | What It Does |
|---|---|
| prd-creator | Writes product requirement docs for complex features |
| technical-designer | Plans architecture and tech stack decisions |
| acceptance-test-generator | Creates E2E and integration test scaffolds from requirements |
| integration-test-reviewer | Reviews integration/E2E tests for skeleton compliance and quality |
| task-executor | Implements backend features with TDD |
| quality-fixer | Runs tests, fixes type errors, handles linting - everything quality-related |
| rule-advisor | Picks the best coding rules for your current task |
| Agent | What It Does |
|---|---|
| technical-designer-frontend | Plans React component architecture and state management |
| task-executor-frontend | Implements React components with Testing Library |
| quality-fixer-frontend | Handles React-specific tests, TypeScript checks, and builds |
The backend plugin includes proven best practices that work with any language:
- Coding Principles - Code quality standards
- Testing Principles - TDD, coverage, test patterns
- Implementation Approach - Design decisions and trade-offs
- Documentation Standards - Clear, maintainable docs
These are loaded as skills and automatically applied by agents when relevant.
The frontend plugin has React and TypeScript-specific rules built in.
When building with AI coding assistants, you often run into:
- Context gets exhausted in long sessions
- Code quality drops over time
- Patterns become inconsistent
- You end up fixing test failures and type errors manually
These plugins fix that by:
- Fresh context for each phase - Specialized agents handle different parts without context exhaustion
- Enforced best practices - Language-agnostic rules (backend) and React patterns (frontend) keep quality consistent
- Automated quality checks - Tests, types, and linting run automatically and get fixed if they fail
- Complete lifecycle - From requirements to implementation to review
The frontend plugin is built specifically for React development:
- Component architecture planning with state management decisions
- React Testing Library integration from the start
- TypeScript-first approach with automatic type generation
- Handles build errors, test failures, and type issues automatically
Built in 2 days - 30 TypeScript files with full test coverage, now running in production.
Built in 1.5 days - Complete creative tool with multi-image blending and character consistency.
The right workflow structure + specialized agents = production-quality code at AI speed.
/implement "Add user authentication with JWT"
# What happens:
# 1. Analyzes your requirements
# 2. Creates design documents
# 3. Breaks down into tasks
# 4. Implements with TDD
# 5. Runs tests and fixes issues
# 6. Reviews against design docs/front-design "Build a user profile dashboard"
# What happens:
# 1. Plans React component structure
# 2. Defines state management approach
# 3. Creates work plan
#
# Then run:
/front-build
# This:
# 1. Implements components with Testing Library
# 2. Writes tests for each component
# 3. Handles TypeScript types
# 4. Fixes lint and build errors/task "Fix validation error message"
# Direct implementation with quality checks
# Works the same in both plugins/review
# Checks your implementation against design docs
# Catches missing features or inconsistencies/diagnose "API returns 500 error on user login"
# What happens:
# 1. Investigator collects evidence from code, logs, git history
# 2. Builds evidence matrix with multiple hypotheses
# 3. Verifier validates findings with ACH and Devil's Advocate
# 4. Solver generates solutions with tradeoff analysis
# 5. Presents actionable implementation steps/reverse-engineer "src/auth module"
# What happens:
# 1. Discovers PRD targets (user value units) from code
# 2. Generates PRD for each feature
# 3. Verifies PRD against actual code
# 4. Reviews and revises until consistent
# 5. Discovers Design Doc targets (technical components)
# 6. Generates Design Docs with code verification
# 7. Produces complete documentation from existing codeIf you're working with undocumented legacy code, this command is designed to make it AI-friendly by generating PRD and design docs. For a quick walkthrough, see: How I Made Legacy Code AI-Friendly with Auto-Generated Docs
claude-code-workflows/
βββ .claude-plugin/
β βββ marketplace.json # Manages both plugins
β
βββ agents/ # Shared agents (symlinked by both plugins)
β βββ code-reviewer.md
β βββ investigator.md # Diagnosis workflow
β βββ verifier.md # Diagnosis workflow
β βββ solver.md # Diagnosis workflow
β βββ scope-discoverer.md # Reverse engineering workflow
β βββ code-verifier.md # Reverse engineering workflow
β βββ task-executor.md
β βββ technical-designer.md
β βββ ... (17 agents total)
β
βββ commands/ # Shared commands
β βββ implement.md
β βββ design.md
β βββ diagnose.md # Problem diagnosis
β βββ reverse-engineer.md # Reverse documentation
β βββ plan.md
β βββ build.md
β βββ ... (8 commands for backend, 7 for frontend)
β
βββ skills/ # Skills (auto-loaded by agents)
β βββ ai-development-guide/
β βββ coding-principles/
β βββ testing-principles/
β βββ implementation-approach/
β βββ typescript-rules/ # Frontend-specific
β βββ ... (11 skills total)
β
βββ backend/ # dev-workflows plugin
β βββ agents/ # Symlinks to shared agents
β βββ commands/ # Symlinks to shared commands
β βββ skills/ # Symlinks to shared skills
β βββ .claude-plugin/
β βββ plugin.json
β
βββ frontend/ # dev-workflows-frontend plugin
β βββ agents/ # Symlinks to shared agents
β βββ commands/ # Symlinks to shared commands
β βββ skills/ # Symlinks to shared skills
β βββ .claude-plugin/
β βββ plugin.json
β
βββ LICENSE
βββ README.md
Q: Which plugin should I install?
A: Depends on what you're building:
- Backend, APIs, CLI tools, or general programming β Install
dev-workflows - React apps β Install
dev-workflows-frontend - Full-stack projects β Install both
Both plugins can run side-by-side without conflicts.
Q: Can I use both plugins at the same time?
A: Yes! They're designed to work together. Install both if you're building a full-stack app.
Q: Do I need to learn special commands?
A: Not really. For backend, just use /implement. For frontend, use /front-design. The plugins handle everything else automatically.
Q: What if there are errors?
A: The quality-fixer agents (one in each plugin) automatically fix most issues like test failures, type errors, and lint problems. If something can't be auto-fixed, you'll get clear guidance on what needs attention.
Q: SSH authentication error during plugin installation? A: Set up SSH keys for GitHub:
# 1. Check if SSH key already exists
ls ~/.ssh/id_ed25519.pub
# 2. Generate new SSH key (if needed)
ssh-keygen -t ed25519 -C "[email protected]"
# β Press Enter to save to default location
# β Enter a strong passphrase when prompted (recommended for security)
# 3. Add SSH key to ssh-agent
eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519
# 4. Copy public key to clipboard
cat ~/.ssh/id_ed25519.pub
# β Copy the output
# 5. Add to GitHub
# Go to https://github.com/settings/keys
# Click "New SSH key"
# Paste your public key and save
# 6. Test connection
ssh -T [email protected]
# β Should see: "Hi username! You've successfully authenticated..."MIT License - Free to use, modify, and distribute.
See LICENSE for full details.
Happy Coding with Claude Code Workflows! πβ¨