← ClaudeAtlas

dnd-optimizelisted

Compute the optimal Dungeons & Dragons 2024 ("5.5") build under a set of constraints — a locked concept, a dated goal ("this spell as soon as possible"), a role to fill — scored by a deterministic engine against the bundled catalog and the level 1-20 progression tables, never from the model's memory or from optimizer folklore, which is the most edition-mixed content there is. Use to optimize, min-max or theorycraft a D&D 2024 / 5.5 character, compare or rank builds, or reach a target at the earliest legal level — "best build for X", "which of these is better", "when can I get spell X", "je veux ce sort au plus tôt". Do NOT use with no optimization goal, or when "best" means easiest or most beginner-friendly rather than strongest — both are dnd-build; nor for older editions or Pathfinder.
mlabarrere/dungeons-and-skills · ★ 0 · AI & Automation · score 68
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