Hands-on training ground for the Claude Code workflow kit.
Also available on GitLab: gitlab.com/waveeng/ccwork-lab
- Use this template — click "Use this template" on GitHub to create your own copy
- Clone your repo:
git clone <your-repo-url> - Open Claude Code:
cd ccwork-lab && claude - Start the first lab:
/ccwork lab "Project Setup"
| Lab | What You Learn | Time |
|---|---|---|
| 01 - Project Setup | /ccfold, CLAUDE.md, /engage, Dev-Team | ~15 min |
| 02 - Your First Workflow | issue → branch → code → precheck → scp → PR → close | ~15 min |
| 03 - Identity and Check-In | /name, agent identity, /engage, session setup | ~10 min |
| 04 - Code Review | /review, severity ratings, fixing findings | ~15 min |
| 05a - Design Your MCP Server | PRD writing, issue decomposition, /prepwaves | ~20 min |
| 05b - Build and Ship It | /nextwave, flight partitioning, MCP registration | ~30 min |
Labs 05a and 05b are an end-to-end project where you design and build your own MCP tool server. Unlike Labs 01-04 which have guided solutions, you pick what to build — making it a real design exercise, not a tutorial.
The MCP server you build is yours to keep and use with Claude Code.
Each lab supports three learning styles:
- Do it —
/ccwork lab "<name>"guides you hands-on - Watch it — Load
labs/NN/session.jsonlinto Clawback to watch how it was solved - Read it — Browse the issue template and solution tag for static reference
Each lab has a starting branch, an init tag (immutable reset point), and a solution tag:
lab/01-start → lab/01-init (tag) → lab/01-solution (tag)
lab/02-start → lab/02-init (tag) → lab/02-solution (tag)
...
If you need to reset a lab: git checkout -B lab/NN-start lab/NN-init
- Claude Code workflow kit installed (
install.sh --checkall green) - GitHub CLI (
gh) authenticated - Python 3.10+ (for lab exercises)
- Bun runtime (for Lab 05 MCP server)