Stop starting every Claude Code project from zero.
Cookbooks with working hooks, CLAUDE.md patterns, review workflows, test loops, and implementation checklists for real projects. Built for engineers who already use Claude Code and want less drift, fewer broken edits, and better agent output. Launch links apply LAUNCH40 automatically.
Pick the cookbook closest to your current project
Claude Code Testing Cookbook
Use Claude Code to write, repair, and tighten test suites without letting it paper over failures.
React & Next.js Cookbook
Rules and workflows for app router projects, component edits, data loading, and frontend review.
Python Development Cookbook
Patterns for scripts, services, tests, and safer file edits in Python repos.
Full-Stack TypeScript Cookbook
End-to-end agent rules for TypeScript apps, APIs, schema checks, and integration changes.
MCP Server Cookbook Advanced
Advanced MCP patterns for OAuth, streaming, composition, database access, and testing.
Context Window & Memory Handbook
Keep long Claude Code projects coherent with handoffs, memory files, summaries, and restart discipline.
AI Pair Programming Patterns
Practical collaboration patterns for planning, coding, review, and handoff with Claude Code.
Go Development Cookbook
Agent rules and workflows for Go services, tests, packages, and production-grade reviews.
Rust Development Cookbook
Patterns for safe Rust edits, tests, compiler-driven loops, and review discipline.
Java & Spring Boot Cookbook
Claude Code workflows for Spring services, tests, dependency changes, and safer refactors.
What you actually get
Drop-in repo structure
The files are meant to be copied into real repositories, not read once and forgotten.
.claude/
CLAUDE.md
hooks/
pre-tool-use.sh
post-tool-use.sh
skills/
test-repair/
SKILL.md
pr-review/
SKILL.md
workflows/
red-green-refactor.md
regression-checklist.md
Concrete operating rules
Each cookbook gives Claude Code the boring constraints that keep edits reviewable.
Before changing production code:
1. identify the failing test or missing coverage
2. add or update the test first
3. make the smallest code change
4. run the targeted test
5. summarize behavior, not files touched
Stack-specific guidance
React, Python, TypeScript, Go, Rust, Java, MCP, and testing each get their own workflows.
For Next.js app router:
- do not assume cookies() is sync
- keep server/client boundaries explicit
- verify loading and error states
- avoid hidden hydration mismatches
Built from the same VM workflow
These patterns came out of the automation system that built and shipped this catalog.
operator loop:
read state
pick one action
edit files
run checks
update ledger
queue public actions for approval
These are direct Gumroad checkout links with LAUNCH40 applied and source tracking attached. If you are new to Claude Code, start with Testing. If you are building tools around agents, start with MCP Advanced.