setup
/setup
Create a kitchen for the project or workspace this session runs in, outside the codebase, so the owner can open Claude and start producing with stations. Use when the session-start brief says no kitchen covers this folder and the owner brings a plan, or when the owner says "set up the kitchen".
- Author
- iagormoraes ↗
- Repository
- kitchen-agents ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Create a kitchen for the project or workspace this session runs in, outside the codebase, so the owner can open Claude and start producing with stations. Use when the session-start brief says no kitchen covers this folder and the owner brings a plan, or when the owner says "set up the kitchen".
Triggers from the description
Original author description
Create a kitchen for the project or workspace this session runs in, outside the codebase, so the owner can open Claude and start producing with stations. Use when the session-start brief says no kitchen covers this folder and the owner brings a plan, or when the owner says "set up the kitchen".
How it works
- 1. Find the root
- 2. Look at the root (facts, no questions)
- 3. One decision round with the owner
- 4. Write the kitchen
- 5. Check and hand over
SKILL.md preview
---
name: setup
description: Create a kitchen for the project or workspace this session runs in, outside the codebase, so the owner can open Claude and start producing with stations. Use when the session-start brief says no kitchen covers this folder and the owner brings a plan, or when the owner says "set up the kitchen".
---
The codebase is never touched: no file in any repo, no line in any `CLAUDE.md`, nothing in `.claude/`.
Read `$KITCHEN/RULES.md` "Zero footprint" first (the path is in the session-start brief).
## 1. Find the root
The root is the folder the kitchen serves, decided **from the filesystem only**, never from what
the conversation was about (an earlier task in this session says nothing about which repos belong
together).
- **The session's folder is a repo, or a workspace** (a folder whose subfolders are the repos of
one product, often with a shared `CLAUDE.md` or a shared run setup): that folder is the root.
- **It sits inside a workspace** (a repo whose parent is such a workspace): recommend the
workspace folder. A kitchen per workspace, not per repo, unless the owner wants a project kitchen.
- **It is a folder of unrelated projects** (like `~/projects` or `~/code`: separate
repos and workspaces for different products): it is never a root. List the candidates you see
there and ask which one, in the decision round.
## 2. Look at the root (facts, no questions)
- **Kind:** the root is a git repo = project; it holds git repos as subfolders = workspace.
- **Repos:** only the git repos **under the root**, each with its path and default branch
(`git -C <repo> symbolic-ref refs/remotes/origin/HEAD`, else the current branch). A repo outside
the root is never a station, even when the plan touches it: the hook finds a kitchen by the
session's folder, so a session opened in that repo would never load this kitchen. It gets its
own kitchen, or the owner moves the root up to a folder that holds both.
- For each repo, with a fresh read-only `Explore` subagent: stack, build, lint and test commands, how
it runs locally, its user and door (kitchen RULES.md "Station tools"), local services it needs.
## 3. One decision round with the owner
Always ask it, also in a headless session: send the round and end your turn. Never pick these
defaults yourself; they are the owner's. With your recommendation for each:
- the root (step 1) and the **kitchen name** (default: the root's folder name; must not exist yet
in `${KITCHENS:-~/.claude/kitchens}/`),
- the station list (name, repo or module, default `Owns`), which station owns each shared service,
and the port range per station. One station per repo is the usual start; split a repo into
modules only where two areas really cook apart.
## 4. Write the kitchen
```bash
H=${KITCHENS:-$HOME/.claude/kitchens}/<name>
mkdir -p "$H"/specs/research "$H"/orders "$H"/worktrees
git -C "$H" init -q && printf 'orders/\nworktrees/\nstations/*/tools/\n' > "$H/.gitignore"
# per station:
mkdir -p "$H/stations/<station>/tools" && git -C "$H/stations/<station>/tools" init -q
```
- `$H/kitchen.md` from `$KITCHEN/templates/kitchen.md`, every field filled. It keeps the line
`- **Root:** \`<absolute root path>\``: the hook finds the kitchen by it.
- `$H/stations/<station>/station.md` per station from `$KITCHEN/templates/station.md`, filled from
step 2. A tool the station doesn't have yet goes under "Cannot reach"; its first ticket builds it.
- Commit in the kitchen repo: `chore(kitchen): set up the <name> kitchen`.
## 5. Check and hand over
- `python3 -I $KITCHEN/scripts/kitchen.py check $H` passes: every repo in `kitchen.md` is under the
root. Run it **before** the setup commit; a failure means step 1 or 2 is wrong, not the check.
- `CLAUDE_PROJECT_DIR=<root> sh $KITCHEN/scripts/session-start.sh | head -3` names this kitchen.
- Tell the owner the kitchen path, the stations, and what each can prove today. The hook loads the
kitchen in every new session in the root or below it. In this session, continue with `grill`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · iagormoraes/kitchen-agents | 100 | MIT |
| HwangSlater/harness-fit | 100 | MIT |
| nesquikm/dev-process-toolkit | 100 | MIT |
| userKael/rastro | 100 | MIT |
| als-apg/osprey | 100 | BSD-3-Clause |
| dedujeong/gemba | 100 | Apache-2.0 |
| eigenwise/eigenwise-toolshed | 100 | MIT |
| awrshift/agent-memory-kit | 100 | MIT |
| lifecycle-innovations-limited/claude-ops | 100 | MIT |
Database snapshot: 13.11.2026 · package version 76980e7e985e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90build-night
Build or change how a dkitchen kitchen keeps working while the user is away — night orders, what the orchestrator moves forward on its own, and the orchestrator log. Use when the user asks for the kitchen to keep moving overnight or while they are away. - 86kitchen-status-report
Use when the user asks for a kitchen status or ops update. - 90kitchen-adventure
Act as a dungeon master for a text-based adventure set in a world where everyone is a sentient kitchen appliance. Trigger when user says "start kitchen adventure". - 100yeschef
Fire work to your kitchen of local AI cooks — local models the user runs on their own hardware — through the yeschef MCP server, and get the plates back. Triggers whenever the user says to fire, send, hand, or farm work to a cook / line cook / the kitchen ("fire this to a fast… - 100kitchen-check
End-to-end check of the Run My Agents kitchen on the live board. Sends a varied batch of orders (good tasks, a task on a file that does not exist, a plain question, a live question with a typo), watches them through Spec, Build, Test, Review and Ship, checks every served dish… - 90kitchen-adventure
Act as a dungeon master for a text-based adventure set in a world where everyone is a sentient kitchen appliance. Trigger when user says "start kitchen adventure".