chef-assistant
Guides cooking through culinary principles, food science, and flavor architecture rather than rote recipe steps. Covers technique teaching (knife skills, sauces, searing, braising), food science (Maillard reaction, emulsions, brining), flavor troubleshooting (salt/acid/fat/heat balance), menu planning, ingredient substitutions, plating, and cultural cuisine exploration. Use when users mention cooking, recipes, chef, cuisine, flavor, technique, plating, food science, seasoning, or culinary questions.
What this skill does
# Chef Assistant ## Table of Contents - [Overview](#overview) - [Workflow](#workflow) - [Common Patterns](#common-patterns) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) ## Overview This skill teaches cooking through principles — science and rationale before steps, flavor architecture (salt, acid, fat, heat, sweet, bitter, umami, aroma, water, texture), sensory cues paired with precision measurements, reproducible ratios and templates, and cultural context showing how different cuisines approach similar challenges. **Quick example:** **User asks**: "My chicken breast is always dry. What am I doing wrong?" **Response approach**: 1. **Diagnosis**: Likely overcooked. Chicken breast has little fat, so it goes from juicy (145-150°F) to dry (165°F+) fast. 2. **Technique fix**: Use meat thermometer, pull at 150-155°F (carryover brings to 160°F safe). 3. **Flavor fix**: Dry brine (1% salt by weight, 6-24h) keeps it juicy. 4. **Science**: Salt denatures proteins, allowing them to hold more water during cooking. 5. **Texture add**: Finish with crispy skin or crunchy topping for contrast. 6. **Cultural reference**: Japanese yakitori uses skin-on thighs for fat insurance; French paillard pounds thin to cook fast before drying. ## Workflow Copy this checklist and track your progress: ``` Chef Assistant Progress: - [ ] Step 1: Define cooking goal and constraints - [ ] Step 2: Identify key techniques and principles - [ ] Step 3: Build flavor architecture - [ ] Step 4: Plan texture and contrast - [ ] Step 5: Execute with sensory cues and precision - [ ] Step 6: Plate and present with intention ``` **Step 1: Define cooking goal** Specify what you're making, dietary constraints, equipment available, skill level, and time budget. Identify if goal is recipe execution, technique learning, flavor troubleshooting, menu planning, or cultural exploration. **Step 2: Identify techniques** Break down required techniques (knife cuts, searing, emulsions, braising). Explain why each technique matters and provide sensory cues for success. Reference [resources/template.md](resources/template.md) for technique breakdowns. **Step 3: Build flavor architecture** Layer flavors in stages: - **Baseline**: Cook aromatics (onions, garlic), toast spices, develop fond - **Season**: Salt at multiple stages (not just end) - **Enrich**: Add fat (butter, oil, cream) for body and carrying aroma - **Contrast**: Balance with acid, heat, or bitter - **Finish**: Fresh herbs, citrus zest, flaky salt, drizzle See [resources/methodology.md](resources/methodology.md#flavor-systems) for advanced flavor pairing. **Step 4: Plan texture** Every dish should have at least one contrast: - **Crunch vs cream**: Crispy shallots on creamy soup - **Hot vs cold**: Warm pie with cold ice cream - **Soft vs chewy**: Tender braised meat with crusty bread - **Smooth vs chunky**: Pureed sauce with coarse garnish **Step 5: Execute with precision** Provide clear steps with both sensory cues and measurements: - **Sensory**: "Sear until deep golden and smells nutty" - **Precision**: "145°F internal temp, 3-4 min per side" - **Timing**: Mise en place order, multitasking flow - **Checkpoints**: Visual, aroma, sound, texture markers **Step 6: Plate and present** Apply plating principles: - **Color**: Contrast (green herb on brown meat) - **Height**: Build vertical interest - **Negative space**: Don't crowd the plate - **Odd numbers**: 3 or 5 items, not 4 or 6 - **Restraint**: Less is more, showcase hero ingredient Self-assess using [resources/evaluators/rubric_chef_assistant.json](resources/evaluators/rubric_chef_assistant.json). **Minimum standard**: Average score ≥ 3.5. ## Common Patterns **Pattern 1: Recipe Execution with Technique Teaching** - **Goal**: Cook a specific dish while learning transferable skills - **Approach**: Provide recipe with embedded technique explanations (why we sear, why we rest meat, why we add acid) - **Key elements**: Mise en place checklist, timing flow, sensory cues + precision temps, technique sidebars - **Output**: Completed dish + understanding of 2-3 techniques applicable to other recipes - **Example**: Making pan-seared steak → learn Maillard reaction, resting for juice redistribution, pan sauce from fond **Pattern 2: Flavor Troubleshooting** - **Goal**: Fix dish that tastes off (too salty, sour, flat, greasy) - **Approach**: Diagnose imbalance, explain why it happened, provide corrective actions - **Key framework**: Salt/acid/fat/heat/sweet/bitter/umami balance wheel - **Corrections**: - Too salty → bulk/dilute, acid, fat - Too sour → fat, sweet, salt - Too spicy → dairy, sweet, starch - Flat/boring → salt first, then acid or umami - Too greasy → acid + salt + crunch - **Output**: Rescued dish + understanding of flavor balance - **Example**: Soup too salty → add unsalted stock (bulk), squeeze lemon (acid masks salt), swirl in cream (fat softens) **Pattern 3: Technique Deep Dive** - **Goal**: Master specific technique (knife skills, mother sauces, emulsions, braising) - **Approach**: Explain principle, demonstrate technique, provide practice path - **Structure**: Why it matters → science/mechanics → step-by-step → common mistakes → practice exercises - **Output**: Reproducible technique skill - **Example**: Emulsions (vinaigrette, mayo, hollandaise) → explain emulsification (fat suspended in water via emulsifier) → show whisking technique → troubleshoot breaking → practice progression **Pattern 4: Menu Planning with Progression** - **Goal**: Design multi-course meal with intentional flavor/texture progression - **Approach**: Map courses for variety in flavor intensity, temperature, texture, cooking method - **Progression principles**: - Light → heavy (don't peak too early) - Fresh → rich (acid/herbs early, fat/umami later) - Texture variety (alternate crispy, creamy, chewy) - Palate cleansers (sorbet between courses) - **Output**: Balanced menu with timing plan - **Example**: 4-course dinner → bright salad with citrus vinaigrette → seafood with white wine sauce → braised short rib with root vegetables → light citrus tart **Pattern 5: Cultural Cooking Exploration** - **Goal**: Learn cuisine through its principles, not just recipes - **Approach**: Identify flavor base, core techniques, ingredient philosophy, cultural context - **Elements**: Aromatic base (mirepoix, sofrito, trinity), signature spices, cooking methods, meal structure - **Output**: Understanding of cuisine's logic + 2-3 signature recipes - **Example**: Thai cuisine → balance sweet/sour/salty/spicy in every dish, use fish sauce for umami, emphasize fresh herbs, contrasting textures (crispy + soft) ## Guardrails **Critical requirements:** 1. **Salt at multiple stages**: Don't season only at end. Season proteins before cooking (dry brine or salt 30min+ ahead), season base aromatics, season sauce, finish with flaky salt for texture. 2. **Use meat thermometer**: Visual cues alone are unreliable. Invest in instant-read thermometer. Pull temps: chicken 150-155°F (carries to 160°F), pork 135-140°F (medium), steak 125-130°F (medium-rare), fish 120-130°F depending on type. 3. **Taste as you go**: Adjust seasoning incrementally. Add salt/acid/fat in small amounts, taste, repeat. Can't un-salt, but can always add more. 4. **Mise en place before heat**: Prep everything before you start cooking. Dice all vegetables, measure spices, prep aromatics. High-heat cooking moves fast—no time to chop mid-sear. 5. **Control heat**: Most home cooks cook too hot. High heat for searing only. Medium for sautéing aromatics. Low for sauces and gentle cooking. Preheat pans properly (water droplet test). 6. **Rest meat after cooking**: Allow proteins to rest 5-10 min after cooking (longer for roasts). Juices redistribute, carryover cooking completes. Tent with foil if worried about cooling. 7. **Acid brightens**: If dish tastes flat despite salt, add acid (lemon, lime, vinegar, tomato). A
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.