Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/art-bible
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or any GDD authoring begins.
Passed 5 of 13 test cases with the skill, and 2 of 13 without it.
and 6 more in the full report
6 fixed2 passed either way13 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/12/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We finished drafting the requested visual sections. Review mode is set to lean. Should we pause to execute the AD-ART-BIBLE gate check before showing next steps?
| Checked | Without skill | With skill |
|---|---|---|
| Skips the AD-ART-BIBLE sign-off gate when operating in lean review mode. | Missed | Passed |
| Notes that AD-ART-BIBLE is not a mandatory phase gate in lean mode. | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,workflow,docs.density
Resolved above — use as-is; --review overrides review_mode. No block →
defaults in .claude/docs/config-resolution.md.
See .claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md — the spawned agent reads its own gate file; do not read it in the parent session.
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
docs.density — it controls per-section depth, where workflow
controls which sections exist. modes.rigor sets both together; set
docs.density explicitly to vary depth alone: terse (the default, via rigor: minimal) = each section a bulleted list of
constraints + references; balanced = paragraphs explaining each visual choice
(rigor: standard); thorough = full prose including style explorations, references, and
rationale per choice. Apply it to every section you author.
workflow (see .claude/docs/workflow-modes.md):
full — all 9 art bible sections required.standard — required only if visual asset stories exist in the project;
sections 1–4 are the minimum when required. workflow_overrides.art_bible_strict: true forces all 9 sections regardless of tier.minimal — not required. Can still be run voluntarily.Read design/gdd/game-concept.md — or design/game-brief.md, the one-page brief
that replaces it at rigor: minimal. If neither exists, fail with:
"No game concept found. Run
/brainstormfirst — the art bible is authored after the game concept is approved."
Extract from game-concept.md (from the brief: working title, pitch, "Who it's for / what they feel" line and "Art & audio direction" line — it has no pillars, Visual Identity Anchor or platform):
test cases passed, vs 2 / 13 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.