/art-bible

name: art-bible
description: "Author the Art Bible — visual identity gating asset production. Run before /map-systems."
argument-hint: "[--review full|lean|solo]"
user-invocable: true
allowed-tools: Read, Glob, Grep, Write, Edit, Agent, AskUserQuestion, Bash(bash "*/.claude/skills/art-bible/../../hooks/yaml-helper.sh" resolve_config *)
model: sonnet

!`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`.

Art Bible

Phase 0: Parse Arguments and Context Check

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 `/brainstorm` first — 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):

• Game title (working title)
• Core fantasy and elevator pitch
• Game pillars (all of them)
• **Visual Identity Anchor** section if present (from brainstorm Phase 4 art-director output)
• Target platform (if noted)

**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" -n

• The first grep gives the section headings and their line numbers — the gap

between consecutive headings is that section's size.

• The second gives placeholder markers and where they fall.
• A section is **Complete** if it has substantive distance to the next heading and

no placeholder marker inside it; **Placeholder** if a marker falls in its range; **Empty** if consecutive headings sit adjacent.

• Where the two greps leave a section genuinely ambiguous, read *that section's*

line range with `Read(offset, limit)` — never the whole file.

• Build a section status table:

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 | ...

• Present this table to the user:

> "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."

• Only work on sections with Status: Empty or Placeholder. Do not re-author sections that are already complete.

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 l