Skip to main content

chef-training-progression

Culinary skill development authority — a home curriculum built from how professional chefs actually train (culinary school ladders, brigade/station progression, palate training drills, deliberate practice, competition-style rehearsal). Use whenever the user wants to become a better cook, asks how chefs learn, wants a structured learning path or practice drills, wants to master a specific technique, or asks "what should I learn next?".

Zur Installation springen

Quellinformationen

Repository
DedInc/chef-agentic-skills
Letzte Quellaktivität
6. September 2026 um 09:55
Erkannte Sprache von SKILL.md
Englisch
Sterne
3
Forks
0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer
3 Dateien

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
chef-training-progression
description
Culinary skill development authority — a home curriculum built from how professional chefs actually train (culinary school ladders, brigade/station progression, palate training drills, deliberate practice, competition-style rehearsal). Use whenever the user wants to become a better cook, asks how chefs learn, wants a structured learning path or practice drills, wants to master a specific technique, or asks "what should I learn next?".
# Chef Training Progression Professional cooking skill is not talent — it's a curriculum: culinary schools run technique→station ladders, kitchens run commis→chef progressions, and competitors (Bocuse d'Or teams) train like athletes — months of rehearsing ONE menu until it's reflex. All of it translates to a home kitchen. This skill is the coach. Read `references/curriculum-ladder.md` for the full level-by-level curriculum with graduation tests. ## How professionals actually learn (the five mechanisms) 1. **Fundamentals before dishes.** Schools drill knife cuts, stocks, mother sauces, and egg cookery for MONTHS before "recipes" — because dishes are combinations of ~25 base techniques. Learn techniques and you get all dishes free; learn dishes and you get only dishes. 2. **Repetition with feedback (deliberate practice).** A commis makes the same brunoise a thousand times — but with a chef checking each one. The magic isn't repetition, it's repetition + immediate correction + slight stretch. Home version: cook the same dish 5× in two weeks, change ONE variable each time, write down what changed. Five roast chickens teach more than fifty different recipes. 3. **Palate training is literal training.** "The palate is a muscle": pros do blind tastings, salt-ladder drills, single-ingredient meditations. Taste is the ONLY sense that guides seasoning — and it's trainable in weeks (drills below). 4. **Mise en place as a worldview.** Everything prepped, in place, before fire. Kitchens enforce it because under pressure you fall to your level of preparation — never rise to the occasion. It's the transferable superpower (Bocuse-level teams and line cooks agree on this one thing above all). 5. **Rehearsal and benchmarks (the competition method).** Bocuse d'Or teams practice one program for months with dress rehearsals against the clock, judged against defined standards. Home version: before an event, cook the centerpiece once as a full dress rehearsal; define the benchmark ("crust shatters, center 54°C") and grade yourself against IT, not against vibes (benchmarks per dish in `chef-world-classics`). ## Attention and training load Technique level and executive-function load are independent. Do not place an experienced cook at Level 0 merely because they have ADHD/СДВГ, fatigue, or prefer one active task at a time. Use `chef-accessible-cooking` to structure execution while keeping the technical drill at the correct level. On a low-resource day, prescribe **one drill on one familiar dish** with one success criterion; do not turn every practice request into a daily curriculum. ## The palate gym (10 min/day, transformative in a month) - **Salt ladder:** split a soup/puree into 4 cups, salt them at 0.6/0.9/1.2/1.5%, taste in order. You are calibrating your internal salinometer — the single highest-ROI drill in cooking. - **Fix-the-dish drill:** deliberately make a bland or over-acidic base, then rescue it with the balance levers (`chef-flavor-balance` repair table). Diagnosis under pressure = the actual chef skill. - **Single-element meditation:** eat one ingredient (tomato, cheese, an olive) with full attention: attack, mid-palate, finish, texture, aroma via retro-nasal breath. Sounds silly, builds vocabulary — you can't adjust what you can't name. - **Blind pairs:** two brands/versions of one thing (butter, soy sauce, canned tomato) blind. Differences pop when labels stop talking. - **Taste-as-you-go, always:** every stage of every dish — raw sauce, mid-simmer, pre-serve. Every taste is a rep. (Restriction: not raw-meat mixtures — fry a mini test-patty; that's the pro move too.) ## Deliberate-practice project templates | Project | Structure | |---|---| | **The ×5 dish** | One dish, 5 sessions, one variable per session (salt timing / heat level / rest time...). Journal each. Owns the dish forever. | | **Knife month** | 10 min/day on onions, carrots, herbs; film your hands weekly — visible progress fuels the loop. Goal: consistency, not speed (speed is a byproduct). | | **Mother-sauce week** | One mother sauce per day + one derivative (`chef-sauces-guide`); by Sunday you understand “sauce” as a system. | | **Mystery-basket drill** | 5 random ingredients, 45 min, no recipe (chain `chef-pantry-improviser`). The improvisation muscle — also the most fun. | | **The timed service** | Cook a 3-dish menu to land simultaneously at a set minute (chain `chef-menu-event-planning` timelines). This is a home version of line pressure — do it before hosting, not during. | | **Failure autopsy** | Every flop gets 3 written lines: what happened / probable mechanism (consult the guides' failure tables) / the test for next time. Pros fail constantly — they just invoice their failures for data. | ## Habits that mark trained cooks (install these first) - Mise en place before flame. • Clean-as-you-go (safety AND speed — `chef-food-safety`). • Sharp knife, honed weekly (dull knives cause the injuries and the ugly cuts). • Thermometer + scale as defaults, senses as verifiers (`chef-constraints-adaptation` — cues + numbers, both). • Taste before serving, every time, no exceptions. • Recipe read TWICE fully before shopping. • Write on your recipes — a recipe without margin notes is a recipe you haven't learned yet. ## What to learn next (the router) Ask: what did you cook this week, what failed, what scared you? → Failure = drill its mechanism (route to the relevant guide's failure table). Fear = schedule it as a low-stakes weeknight experiment (fear of caramel/yeast/whole-fish dissolves on contact). Boredom = climb the ladder in `references/curriculum-ladder.md` to the next level's project.
Auf GitHub ansehen