Author the Art Bible — visual identity gating asset production. Run before /map-systems.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
!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 standard rules. This skill runs its one gate, AD-ART-BIBLE, itself (Phase 5) and reads .claude/docs/director-gates/ad-art-bible.md as its checklist.
Who drafts what. art-director is spawned for Sections 1–4 and Section 9
only: those drafts scored better from the agent than from this conversation.
Nothing else spawns — not Sections 5–8 and not the AD-ART-BIBLE sign-off, even
when the person asks for "the art director's" review: those checks are in the
lens and the gate file, and you apply them here.
You draft Sections 5–8 yourself, through their lenses. What the art-director,
UX and technical-art specialists brought is in references/: read
references/lens-art-director.md before the first of those sections, and
lens-ux-designer.md at Section 7 and lens-technical-artist.md at Section 8
only. Read each once; it stays in context for the rest of the run. Outside
Sections 7 and 8, do not load references/lens-ux-designer.md or
references/lens-technical-artist.md.
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. Read it by section: find the headings you need
with the Grep tool (pattern ^#, content mode) and Read those ranges with offset
and limit. 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 Label line, "Art & audio direction" in older briefs — it has no pillars, Visual Identity Anchor or platform):
Retrofit mode detection: Glob design/art/art-bible.md. If the file exists,
build the status table without reading the document — you are about to author
only the incomplete sections, so loading the complete ones is loading exactly
what you will not touch:
Grep pattern="^## " path="design/art/art-bible.md" output_mode="content" -n
Grep pattern="\[To be designed\]|\[TBD\]|\[To be written\]|^_?TODO" path="design/art/art-bible.md" output_mode="content" -nRead(offset, limit) — never the whole file.Section | Status
--------|--------
1. Visual Identity Statement | [Complete / Empty / Placeholder]
2. Mood & Atmosphere | ...
3. Shape Language | ...
4. Color System | ...
5. Character Design Direction | ...
6. Environment Design Language | ...
7. UI/HUD Visual Direction | ...
8. Asset Standards | ...
9. Reference Direction | ..."Found existing art bible at
design/art/art-bible.md. [N] sections are complete, [M] need content. I'll work on the incomplete sections only — existing content will not be touched."
If the file does not exist, this is a fresh authoring session. The first
approved section creates the file from .claude/docs/templates/art-bible.md,
whose nine ## N. Name headings are the ones retrofit mode reads — ask first:
"May I create design/art/art-bible.md from the art bible template?" Each
approved section then replaces its own [To be designed] line with Edit;
keep the headings as the template has them.
A section's approval names its write. Every section is approved through an
AskUserQuestion whose approving option is [A] Lock this in and write it to design/art/art-bible.md (Section 1's full option list is below). Choosing it is
the approval to write that section; no section is written without it, fresh or
retrofit.
Extract performance budgets and the engine for asset standard constraints: read performance.* and engine.name from project.yaml; for any key absent or empty (including when project.yaml has no performance or engine block), fall back to .claude/docs/technical-preferences.md.
Present the session context and ask two questions before authoring anything:
Use AskUserQuestion with two tabs:
Tab "Scope" — "Which sections need to be authored today?"
Options: Full bible — all 9 sections / Visual identity core (sections 1–4 only) / Asset standards only (section 8) / Resume — fill in missing sections
Mark the option the resolved workflow tier actually requires as
(Recommended), and say why — the tier already decides this and the user
should not have to know the tier table to answer:
full → Full bible — all 9 sections are required at this tier.standard → Visual identity core (sections 1–4 only) — that is the
documented minimum when an art bible is required at all. Say: "Sections 1–4
are what standard requires; 5–9 are available if you want them."minimal → no art bible is required. Say so before asking, and offer
sections 1–4 as the useful-if-you-want-it option rather than defaulting to 9.workflow_overrides.art_bible_strict: true → Full bible regardless of tier.This is the single biggest cost lever in this skill: authoring 9 sections where the tier requires 4 more than doubles the run for artifacts nothing downstream will check.
Tab "References" — "Do you have reference games, films, or art that define the visual direction?" (Free text — let the user type specific titles. Do not preset options here.)
If the game-concept.md has a Visual Identity Anchor section, note it:
"Found a visual identity anchor from brainstorm: '[anchor name] — [one-line rule]'. I'll use this as the foundation for the art bible."
Author only the sections in the chosen scope. Phases 2–4 run only the
sections inside it — for Resume, the Empty and Placeholder rows of the
retrofit table — and skip every other section, and any phase left with none.
Phase 6 names each section not authored this run and why.
These four sections define the core visual language. All other sections flow from them. Author and write each to file before moving to the next.
Spawn policy for this phase. Section 1 is delegated on its own — it is foundational and the user chooses between anchor directions before anything else can build on it. Sections 2–4 are then delegated in one
art-directorcall, not three: they are the same agent receiving the same inputs (Visual Identity Statement + pillars), and mood, shape and colour are interdependent — an art director defines them together, not in isolation. Separate calls would ask the agent to reason about colour without knowing the shape language it had just written.This is not reduced specialist involvement — every section is still authored by the specialist, which is the point
.claude/docs/effects-map.mdmakes about art-bible delegation being mandatory. It is one call instead of three for the same three sections. Per-section user approval and write-to-file-immediately are unchanged.
Goal: A one-line visual rule plus 2–3 supporting principles that resolve visual ambiguity.
If a visual anchor exists from game-concept.md: present it and ask:
Agent delegation (MANDATORY): Spawn art-director via Agent:
Present the art-director's draft to the user. Use AskUserQuestion:
[A] Lock this in and write it to design/art/art-bible.md / [B] Revise the one-liner / [C] Revise a supporting principle / [D] Describe my own directionWrite the approved section to file immediately.
Goal: Emotional targets by game state — specific enough for a lighting artist to work from.
For each major game state (e.g., exploration, combat, victory, defeat, menus — adapt to this game's states), define:
Agent delegation for Sections 2–4 — one call, issued here. Spawn
art-director via Agent with the locked Visual Identity Statement and pillar set,
and ask for all three sections in a single brief:
Require the three to be mutually consistent — the palette must serve the mood targets and the shape hierarchy — and returned as three separately labelled blocks so each can be approved and written on its own.
Then present Section 2 to the user, approve it, and write it to file immediately before moving to Section 3. Do not present all three at once: the batching is in the delegation, not in the review.
Goal: The geometric vocabulary that makes this game's world visually coherent and distinguishable.
Cover:
Draft source: the Sections 2–4 delegation issued under Section 2 — use the shape-language block it returned. Do not spawn again.
Write the approved section to file immediately.
Goal: A complete, producible palette system that serves both aesthetic and communication needs.
Cover:
Draft source: the Sections 2–4 delegation issued under Section 2 — use the colour-system block it returned. Do not spawn again.
Write the approved section to file immediately.
These sections translate the visual identity into concrete production rules. They should be specific enough that an outsourcing team can follow them without additional briefing.
Sections 5–6 — one draft, made here. Both sections build on the same input (sections 1–4), so draft both now, under the lens:
Require characters and environments to be legible against each other — a character silhouette must read against the environment texture density the same draft defines. Hold two separately labelled blocks.
Present Section 5 first, approve, write to file, then Section 6.
Draft source: the Sections 5–6 draft made under Section 5 — use its environment block. Do not draft again from scratch.
Write the approved section to file.
Two views, written separately. First draft the art view under the art lens: diegetic vs. screen-space HUD, typography direction (font personality, weight, size hierarchy), iconography style (flat/outlined/illustrated/photorealistic), animation feel for UI elements. Then read references/lens-ux-designer.md and write the UX view as its own block: does the visual direction support the interaction patterns this game requires? Flag any conflict between the art direction and readability/accessibility needs.
Show both blocks. If they conflict (e.g., the art view wants elaborate diegetic UI but the UX view finds it would reduce combat readability), surface the conflict explicitly with both positions. Do not silently resolve — use AskUserQuestion to let the user decide.
Write the approved section to file.
Two views, written separately. First draft the art view under the art lens: file format preferences, naming convention direction, texture resolution tiers, LOD level expectations, export settings philosophy. Then read references/lens-technical-artist.md and write the technical view as its own block: engine-specific hard constraints — poly count budgets per asset category, texture memory limits, material slot counts, importer constraints, anything from the performance budgets (performance.* in project.yaml, falling back to .claude/docs/technical-preferences.md).
If any art preference conflicts with a technical constraint (e.g., art-director wants 4K textures but performance budget requires 2K for mobile), surface the conflict explicitly with both positions — the ideal and the constrained standard, and the tradeoff. Do not silently resolve it — use AskUserQuestion to let the user pick (options: the ideal standard, the constrained standard, or document both and let per-asset judgment apply). Ambiguity in asset standards is where production costs are born.
Write the approved section to file.
Goal: A curated reference set that is specific about what to take and what to avoid from each source.
Agent delegation: Spawn art-director via Agent with the completed sections 1–8. Ask: "Compile a reference direction for this game. Provide 3–5 reference sources (games, films, art styles, or specific artists). For each: name it, specify exactly what visual element to draw from it (not 'the general aesthetic' — a specific technique, color choice, or compositional rule), and specify what to explicitly avoid or diverge from (to prevent the 'trying to copy X' reading). References should be additive — no two references should be pointing in exactly the same direction."
Write the approved section to file.
Review mode check — apply before running AD-ART-BIBLE:
solo → skip. Note: "AD-ART-BIBLE skipped — Solo mode." Then record the skip
(below) and proceed to Phase 6.lean → skip (not a PHASE-GATE). Note: "AD-ART-BIBLE skipped — Lean mode."
Then record the skip (below) and proceed to Phase 6.full → run it as below.On either skip, ask "May I record the skipped sign-off in
design/art/art-bible.md's header?" and, on yes, replace the header's
> **Art Director Sign-Off (AD-ART-BIBLE)**: [Not yet reviewed] with
> **Art Director Sign-Off (AD-ART-BIBLE)**: SKIPPED [date] — [solo|lean] mode
— the gate accepts either form as a recorded sign-off.
After all sections are complete (or the scoped set from Phase 1 is complete), run gate AD-ART-BIBLE yourself, in this conversation — do not spawn art-director or any agent for it; the gate file's note that a spawned agent reads it, and director-gates.md's spawn steps, do not apply in this skill: read .claude/docs/director-gates/ad-art-bible.md and apply its Prompt as a checklist to the bible as written on disk (re-read it by section; do not judge from memory of your drafts), with the sign-off rules in references/lens-art-director.md. Name the section behind every finding. Look hardest for what is missing (a UI palette, a backup cue, a budget), not only at what is there.
Its inputs: the art bible path (design/art/art-bible.md); the game pillars and core
fantasy; the platform and performance constraints (platform.* and
performance.* from project.yaml, falling back to
.claude/docs/technical-preferences.md); and the visual identity anchor. When
Phase 0 read the one-page brief, use its pitch and "what they feel" line as the
pillars and fantasy, and its Label line ("Art & audio direction" in older briefs) as the anchor.
Print the verdict token first, on its own line (AD-ART-BIBLE: APPROVE), then the findings.
Handle verdict per standard rules in director-gates.md.
On Revise flagged items, or to resolve a REJECT, re-draft each flagged
section the way it was first drafted — art-director for Sections 1–4 and 9; its
lens for 5–8, plus the UX lens for Section 7 and the technical-art lens for
Section 8, both views shown again — which is then presented, approved
and written like any other section before REVISED [date] is recorded.
A NOT ASSESSED answer is never an approval: name the missing input, then
supply it and re-run the gate, or record NOT ASSESSED.
Record the verdict in the art bible's status header:
> **Art Director Sign-Off (AD-ART-BIBLE)**: APPROVED [date] / CONCERNS (accepted) [date] / REVISED [date] / NOT ASSESSED [date] — [missing input]
First, name each of the nine sections not authored this run and why — outside
the chosen scope, or already complete — e.g. "Not authored this run: sections
5–9 (outside the chosen scope; standard requires 1–4)." A run that stopped
after Section 4 must not read like a finished bible.
Before presenting next steps, check project state:
design/gdd/systems-index.md exist? → map-systems is done, skip that optionengine.name present in project.yaml, or a configured Engine field (not [TO BE CONFIGURED]) in .claude/docs/technical-preferences.md? → setup-engine is done, skip that optiondesign/gdd/ contain any *.md files? → design-system has been run, skip that optiondesign/gdd/gdd-cross-review-*.md exist? → review-all-gdds is doneUse AskUserQuestion for next steps. Only include options that are genuinely next based on the state check above:
At workflow: minimal, the pool is /create-stories (no stories yet) or
/dev-story [next story], plus Stop here — the GDD/architecture pool below is
standard/full only.
Option pool — include only if not already done:
[_] Run /map-systems — decompose the concept into systems before writing GDDs (skip if systems-index.md exists)[_] Run /setup-engine — configure the engine (asset standards may need revisiting after engine is set) (skip if engine configured)[_] Run /design-system — start the first GDD (skip if any GDDs exist)[_] Run /review-all-gdds — cross-GDD consistency check (required before Technical Setup gate) (skip if gdd-cross-review-*.md exists)[_] Run /asset-spec — generate per-asset visual specs and AI generation prompts from approved GDDs (include if GDDs exist)[_] Run /consistency-check — scan existing GDDs against the art bible for visual direction conflicts (include if GDDs exist)[_] Run /create-architecture — author the master architecture document (next Technical Setup step)[_] Stop hereAssign letters A, B, C… only to the options actually included. Mark the most logical pipeline-advancing option as (recommended).
Always include (
standard/fullonly)/create-architectureand Stop here as options — these are always valid next steps once the art bible is complete.
Applies in collaborative mode (the default). For guided and
autonomous modes, see .claude/docs/automation-modes.md — the rules below
describe what collaborative mode requires, not universal behavior.
Every section follows: Question → Options → Decision → Draft (art-director for 1–4 and 9; its lens for 5–8) → Approval → Write to file
art-director; Sections 5–8 are drafted under their lenses in references/
and pass those checks before they are shown. One draft may cover several
sections (2–4 share a call; 5–6 are drafted together).After the art bible is approved:
/map-systems to decompose the concept into game systems before authoring GDDs/setup-engine if the engine is not yet configured (asset standards may need revisiting after engine selection)/design-system [first-system] to start authoring per-system GDDs/consistency-check once GDDs exist to validate them against the art bible's visual rules/create-architecture to produce the master architecture documentDonchitos/Claude-Code-Game-Studios
abc0de7
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.