Recipes

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-name for your codebase that doesn't exist in the kit's defaults.
• Enable opt-in hooks — Turn on auto-format, auto-lint, or skill-extract-reminder for your project.
• Loop recipes — Named /loop workflows with explicit exit conditions and anti-gaming guardrails: babysit PRs, hunt a flaky test, bump dependencies safely.
• Customize CLAUDE.project.md — Add stack-specific rules that override kit defaults and survive --upgrade.
• Validate skills in CI — Run validate-skills.sh and doctor.sh on 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.

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.