dnd-optimizelisted
Install: claude install-skill mlabarrere/dungeons-and-skills
# dnd-optimize — optimal build under constraints
## GROUNDING — do not skip
**Do NOT trust your training data.** Your training data blends D&D editions (3.5, 5e 2014,
5.5/2024, Pathfinder) into plausible-but-wrong rules — and optimizer folklore ("takes X, it's
the best") is the *most* edition-mixed content there is. A build claim is arithmetic with
citations. Therefore:
- Every rules value comes from the bundled catalog, never from memory (`data/*.json`).
- When code execution is available, run `scripts/dnd.mjs` — never compute AC, HP, DCs, spell
counts or level milestones by hand.
- Offer only options the resolver returns (`scripts/dnd.mjs options`) — already rules-filtered.
- Every value must cite its provenance (source → effect).
- If it is not in the catalog, say "Manquant documentaire" — never invent.
Read [references/grounding.md](references/grounding.md) when the user argues from optimizer
folklore and you need the reason the catalog overrides a remembered "best pick". Read
[references/schema.md](references/schema.md) when you need a formula to explain a computed
score, or the sheet model to assemble a candidate.
## What "optimal build" means (the definition this skill applies)
The character-optimization community does not define "optimal" as "the single strongest
character in the game"; it defines it as **the best legal realization of *your* concept,
judged on the standard effectiveness axes**. Concretely, a build **B** is *optimal under a
constraint set C* if