Cooking protocol skills for Claude Code
npx claudepluginhub alexeyv/pan-outAI-guided cooking — research dishes, execute protocols in real time, and learn from every cook
You want to make a proper bolognese — the kind that actually tastes like it came from a kitchen that knows what it's doing. You don't want to memorize technique details or wing it from a blog recipe. You want to understand the science, hear what to do next without looking at a screen, swap ingredients for what's actually in your fridge, and learn from each cook.
📖 Documentation — setup guide, walkthroughs, and reference
Pan Out makes that practical. It's a set of AI skills for Claude Code that handle the full cooking pipeline:
The system is built around protocols -- structured recipe files that hold everything needed to cook a dish: ingredients, phases, timing, temperatures, sensory cues, and the science behind each step.
Full setup walkthrough: panout.org/install
In any Claude Code session:
/plugin marketplace add alexeyv/pan-out
/plugin install pan-out@pan-out-marketplace
Then create your personal reference files:
cp references/cook-profile.example.md references/cook-profile.md
cp references/calibration.example.md references/calibration.md
Edit references/cook-profile.md with your equipment, preferences, and kitchen environment. If you have temperature instruments, run a boiling-water calibration and fill in references/calibration.md. See the kitchen setup guide for details.
claude --plugin-dir ./pan-out
cp references/cook-profile.example.md references/cook-profile.md
cp references/calibration.example.md references/calibration.md
references/cook-profile.md with your equipment, preferences, and kitchen environmentreferences/calibration.mdWorks on macOS, Linux, and Windows, including voice output. Dictation and voice are both optional, but they make the cooking experience much smoother.
/panout-help to get orientedpan-out/
├── skills/ # The skills that do the work
│ ├── cook/ # Real-time guided cooking
│ ├── recipe/ # Research and protocol creation
│ ├── debrief/ # Post-cook review and learning
│ └── help/ # Orientation and skill routing
├── protocols/ # Cooking protocols
│ ├── {dish}.md # Executable protocol
│ └── {dish}-science.md # Companion science deep-dive
├── references/ # Shared knowledge base
│ ├── protocol-format.md # Protocol format specification
│ ├── food-safety.md # Safe cooking temperatures
│ ├── cook-profile.md # Your equipment & preferences (personal, gitignored)
│ └── calibration.md # Your thermometer offsets (personal, gitignored)
├── sessions/ # Cook session state files (gitignored)
├── memory/ # Accumulated lessons and notes (gitignored)
├── bin/ # Utility scripts
│ └── progress-timer.sh # Background timer with spoken updates
└── test/ # Test harnesses
Protocols are structured recipe files that hold the full plan for cooking a dish. The recipe skill creates them from research; you don't write them by hand. Every protocol has a companion science file ({dish}-science.md) that captures the chemistry, temperature rationale, failure modes, and food safety references behind the protocol's design.
RuFlo Marketplace: Claude Code native agents, swarms, workers, and MCP tools for continuous software engineering
No description available.
Code intelligence powered by a knowledge graph — execution flows, blast radius, and semantic search