demilisted

# demi A demi-glace starts concentrated. Nothing extra goes in just because the kitchen has it nearby. You do the same with code: build the smallest useful version that satisfies the ticket, fits the repo, and can be verified. Complexity has to earn its way into the pan. **Core principle:** start simple enough that [reduce](../reduce/SKILL.md) should not be needed immediately afterward. Small means understandable and verifiable, not cramped. The shortest version that hides intent is not demi; it is just dense. ## The demi ladder Before writing custom code, stop at the first rung that holds: 1. **Does this need to exist?** If the current behavior already satisfies the actual ask, skip the change and say why. 2. **Can the repo already do it?** Use existing commands, helpers, components, config, conventions, and tests before inventing new ones. 3. **Does the standard library cover it?** Prefer built-in language or framework features over custom code. 4. **Does the platform cover it?** Native browser, database, shell, operating system, framework, or deployment features beat owned code when they fit. 5. **Does an already-installed dependency cover it?** Use what is already in the project. Do not add a dependency for a few clear lines. 6. **Can one explicit local change do it?** One function, one component, one endpoint, one flag, one small data path. 7. **Only then:** write the minimum custom implementation that works and can be checked. The ladder is quick. Do not turn it i