What the Recipes page is for
The Recipes page is where reusable definitions become real agents and teams on your machine. In practice, this is one of the most important entry points in ClawKitchen because it turns ideas and defaults into working structure.Builtin vs custom recipes
ClawKitchen works with two broad recipe sources:- builtin recipes — bundled with the ClawRecipes plugin
- custom recipes — user-editable recipe files stored in your workspace
- builtin recipes are the shipped defaults
- custom recipes are where your own variations and working patterns should live
- use builtin recipes to get started quickly
- create or evolve custom recipes when the setup becomes yours
Common things you do here
From Recipes, you can:- create a team from a recipe
- create an agent from a recipe
- create a custom team recipe
- inspect recipe details
- edit custom recipes
- remove custom recipes
Example: create a team from a builtin recipe
Typical flow:- Open Recipes
- Pick a team recipe
- Choose Create team
- Set the team id
- Decide whether cron jobs should be installed or reconciled during scaffold
- Finish scaffold and move into the Team editor
Example: create an agent from a recipe
Typical flow:- Open Recipes
- Pick an agent recipe
- Choose Create agent
- Set the agent id and display name
- Open the new agent in the editor to refine identity, files, model, or skills
Example: create a custom team
If builtin recipes get you close but not all the way there, ClawKitchen also supports creating a custom team recipe. That is useful when you want:- your own role mix
- custom instructions
- workspace-specific conventions
- a reusable team structure that you can evolve over time
