Claude Code Workflow Recipes
Standardizes software delivery workflows for consulting teams.
16 recipe skills for backend and frontend development: end-to-end feature development, cross-layer fullstack implementation, bug diagnosis, reverse-engineering PRD from code, design documentation, and integration test addition.
- Follow a step-by-step recipe for building a complete feature
- Diagnose and fix bugs using a structured investigation workflow
- Reverse-engineer project requirements from an existing codebase
Standardizes software delivery workflows for consulting teams. The reverse-engineer and diagnose recipes are particularly valuable for legacy system analysis on client codebases.
Software consulting teams who want structured, repeatable AI-assisted development workflows for feature delivery, bug investigation, and legacy codebase analysis.
https://github.com/shinpr/claude-code-workflows
By shinpr
How to Get It
This is a methodology or approach. Paste the instructions below into a Claude conversation to get started.
Claude Code Workflow Recipes is a toolkit of commands, skills, and configs. See the source link above for the full collection — pick the pieces relevant to your workflow. Paste the source URL into a Claude conversation and ask: "Read this and help me adapt the relevant parts to my project."
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me follow a step-by-step recipe for building a complete feature
Trust Signals Auto-scanned
Community Pulse Active
Discussed on Hacker News, Reddit
- Claude is down — Reddit · 2044 pts
- I reverse-engineered the workflow that made Manus worth $2B and turned it into a — Reddit · 1053 pts
- Claude Code workflow tips after 6 months of daily use (from a senior dev) — Reddit · 801 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 593 GitHub stars; 3 contributors; last commit 6d ago; license MIT.
Things to check
- These are recipe templates, not automation—they still require human judgment to adapt to your tech stack and code patterns. Quality output depends on team discipline in following the workflow structure consistently.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 593 GitHub stars; 3 contributors; last commit 6d ago; license MIT.