Recipes
Recipes
Task-specific how-to guides for common Claude Code Kit workflows.
Step-by-step guides for the workflows people actually run into. The rest of the docs explains what the kit does; this section explains how to do specific things.
Available recipes
- Add a project-specific skill — Create a custom
/skill-namefor your codebase that doesn't exist in the kit's defaults. - Enable opt-in hooks — Turn on
auto-format,auto-lint, orskill-extract-reminderfor your project. - Customize CLAUDE.project.md — Add stack-specific rules that override kit defaults and survive
--upgrade. - Validate skills in CI — Run
validate-skills.shanddoctor.shon every PR via GitHub Actions. - Migrate from Cursor rules — Coming from
.cursorrules? Here's how to port your conventions to the kit. - Multi-project setup — Using the kit across N repos: shared lessons, per-project overlays, upgrades.
Each recipe is self-contained — you can jump to any one without reading the others. They assume you've installed the kit (npx @tansuasici/claude-code-kit init).
When to write a new recipe
If you find yourself doing something three times that isn't in the docs, that's recipe-worthy. Open a PR — the contributing path is the same as for any kit change.