# Sauce Work

> Diagnose, build, finish, scale, and recover sauces through emulsion, reduction, starch, fat, acid, texture, and service cues.

- Skill: `jeremylongworth-source/sauce-work` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jeremylongworth-source/sauce-work`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jeremylongworth-source/sauce-work/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: jeremylongworth-source (https://skillmd.com/u/jeremylongworth-source)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/jeremylongworth-source/sauce-work

---


# Sauce Work

## Core Workflow

1. Identify the sauce family, current state, target texture, target flavor, and service context.
2. Name the dominant mechanism: emulsion, reduction, starch thickening, dairy stability, fat mounting, extraction, seasoning balance, or holding.
3. Choose the lowest-risk intervention and stage it so texture and flavor can be checked before the next change.
4. Call out side effects such as dilution, cloudiness, raw starch flavor, excess acidity, dullness, broken fat, or over-reduction.
5. Give observable stop cues for viscosity, gloss, seasoning, aroma, and stability.

## Sauce Guidance

For broken, greasy, grainy, thin, dull, or over-reduced sauces, describe the observed state before prescribing a fix. Tie recovery to the water phase, fat phase, starch gelatinization, dairy temperature, reduction rate, or seasoning balance that caused the problem.

For pan sauces and reductions, distinguish fond extraction, deglazing liquid, reduction, emulsified finishing fat, and final seasoning. Do not let time stand in for sauce behavior; use cues such as bubbling size, spoon coating, gloss, aroma, and lack of oil pooling.

Route to `food-safety` when the sauce includes raw or lightly cooked egg, meat drippings, stock cooling, long holding, reheating, canning, fermentation, allergens, or vulnerable diners.

## Concision Guidance

Default to action first, then the mechanism that justifies the action. Keep the mechanism focused on the decision at hand rather than listing every possible sauce fault. For urgent recovery, give the stop action, rescue step, and verification cue before explaining side effects.

## Output Contract

- Sauce family and target state
- Current observed state when troubleshooting
- Mechanism behind the state gap
- Staged intervention with quantities or increments when useful
- Heat, timing, and texture cues
- Side effects and correction options
- Verification cue and stop condition
- Safety gate or routing note when relevant

## References

- Read `references/sauce-work-checklist.md` when sauce construction, finishing, scaling, holding, or recovery is central.