Menu
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /ags-brainstorm is approved and before /ags-map-systems or any GDD authoring begins.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /ags-design-review.
Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /ags-project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
| name | ags-art-bible |
| description | Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /ags-brainstorm is approved and before /ags-map-systems or any GDD authoring begins. |
| argument-hint | [no arguments] |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Write, Edit, Task, AskUserQuestion, Bash |
Language: Talk to user in language from .ags/project/user-interaction.md. Fall back to English if file missing. Files on disk always English per .ags/rules/user-interaction.md.
Template is SSoT. Skill does NOT enumerate sections, agents, or modes — it parses .ags/templates/t_art-bible.html at runtime and derives the work plan from it. Editing the template (adding a section, changing an agent assignment, marking a section status-only) propagates to skill behavior with no skill edits required.
Output file: design/art/ags-art-bible.html.
Each authored block is <section id="..." [data-*]>:
| Attribute | Purpose | Default |
|---|---|---|
id | Stable identifier for the section | required |
<h2> (first child) | Display heading | required |
data-agent | Primary agent to spawn for drafting | art-director |
data-consult | Comma-separated agents spawned in parallel for cross-domain check | none |
data-mode | creative (draft via agent) or status (system-recorded, no creative draft) | creative |
data-design-md | co-author (skill must co-author DESIGN.md entries before approval) or lint-required (re-run lint before approval) | none |
data-depends-on | |-separated list of upstream sources this section reads. Each entry: <path> (full file), <path>:<scope> (namespace inside DESIGN.md, e.g. colors,components), <path>#<section-id> (specific section), or self#<section-id> (sibling section in same art-bible) | none |
data-checked-at | ISO date (YYYY-MM-DD) — when the section was last validated against its data-depends-on sources | empty |
data-checked-against | |-separated git blob hashes (one per data-depends-on entry, same order) — snapshot of upstream content at last validation | empty |
Document-level status uses <meta name="status" content="draft|approved"> and <meta name="approved-at" content="YYYY-MM-DD"> in <head>. See .ags/rules/document-boundaries.md.
Read design/gdd/game-concept.md. If missing, fail:
"No game concept found. Run
/ags-brainstormfirst — the art bible is authored after the game concept is approved."
Extract from game-concept.md:
Read template .ags/templates/t_art-bible.html. Parse every <section ...> block. For each, extract:
id<h2> text (display heading)data-agent (default art-director)data-consult (split on comma, trim; default empty)data-mode (default creative)data-design-md (default none)This list IS the work plan. Skill iterates it. Skill MUST NOT inject sections not present in template, skip sections present in template, or reorder them.
Retrofit mode detection: Glob design/art/ags-art-bible.html. If exists:
<section id> from the template plan, locate same id in existing fileComplete (body contains real content, no .placeholder / [bracketed] stubs left) or Empty/Placeholder"Found existing art bible at
design/art/ags-art-bible.html. [N] sections complete, [M] need content. I'll work on incomplete sections only — existing content will not be touched."
AskUserQuestion. Do not silently drop.If file does not exist, fresh authoring session — proceed.
Read .ags/rules/technical-preferences.md if exists — extract performance budgets and engine for technical constraints.
Read .ags/rules/design-system.md — DESIGN.md is canonical token format.
Glob design/art/DESIGN.md:
data-design-md="co-author".Use AskUserQuestion with two tabs:
Full bible — all [N] sections / Resume — fill in missing sections / Custom — pick sectionsIf game-concept.md has Visual Identity Anchor:
"Found a visual identity anchor from brainstorm: '[anchor name] — [one-line rule]'. I'll use this as foundation."
Initialize output file (if not retrofit): Copy .ags/templates/t_art-bible.html to design/art/ags-art-bible.html. Replace <h1> placeholder with game title. Set <meta name="last-updated"> to today. Keep <meta name="status" content="draft">.
Iterate over parsed sections in template order. Skip sections excluded by user scope (Phase 1) and sections marked Complete in retrofit mode.
For each section, run the protocol matching its data-mode:
creative (default)Brief: prepare context for the section. Always include:
.ags/rules/technical-preferences.md for technical constraints)Agent spawn:
data-agent via Task with brief. Ask: "Draft the section titled '[heading]'. Use the placeholder body as guidance for what this section must cover. Anchor in stated pillars and prior sections. Do not invent sub-structure beyond what the placeholder body shows."data-consult non-empty, spawn each listed agent in parallel (single message, multiple Task calls). Each consult agent gets same brief + role-specific question (e.g. ux-designer: "Does the proposed art direction support readability/accessibility for the interaction patterns this game requires? Flag conflicts."; technical-artist: "Are any proposed art preferences in conflict with the engine constraints in .ags/rules/technical-preferences.md?").AskUserQuestion. Do NOT silently resolve.DESIGN.md co-authoring (only if data-design-md="co-author"):
{colors.*}, {typography.*}, {spacing.*}, {rounded.*}, {components.*}) the section citesdesign/art/DESIGN.md (prompt user for values, write to DESIGN.md front-matter)npx @google/design.md lint design/art/DESIGN.md — must return errors=0 before section approvalApproval: present draft via AskUserQuestion:
[A] Lock in / [B] Revise / [C] Describe my own directionWrite to file: replace the entire <section id="X">…</section> block in design/art/ags-art-bible.html with the approved content. Preserve outer markup (the <section> opening tag with its id and data-* attrs, the <h2> heading, sub-section <h3> structure where the placeholder defines it). Replace only .placeholder spans and stub cells with approved content.
Stamp provenance (mandatory on every section approval, including retrofit re-approval):
data-depends-on to a file path. For <path>:<scope> entries, the file is <path> (scope is informational — hash whole file). For <path>#<section> entries, the file is <path>. For self#<id> entries, the file is the art-bible itself (design/art/ags-art-bible.html).git hash-object <path> (works even on uncommitted files). If file is outside git, fall back to sha256sum <path> and prefix with sha256:.data-checked-at on the <section> tag to today's date (YYYY-MM-DD).data-checked-against to |-separated list of hashes (same order as data-depends-on entries).statusSystem-recorded section, no creative draft. Skill fills it from observed project state:
data-design-md="lint-required": run npx @google/design.md lint design/art/DESIGN.md. Record date + errors + warnings count into the section's status fields (look for <dt>Last lint:</dt> or analogous slot in the section's placeholder body). If errors > 0, abort the section and surface the lint output — fix DESIGN.md before retry.AskUserQuestion approval — section is purely factual. Write directly after fields populated.After all in-scope sections complete, spawn creative-director via Task using gate AD-ART-BIBLE (.ags/rules/director-gates.md).
Pass: art bible file path (design/art/ags-art-bible.html), game pillars, visual identity anchor.
Loop exit condition: single iteration where reviewer returns clean (no critical/high/medium findings). Non-clean → user revises affected sections (re-run Phase 2 protocol on those sections), re-spawn same gate. No iteration cap.
Record iteration count and final verdict in art bible by appending to <header class="doc-header">:
<p class="meta"><strong>Art Director Sign-Off (AD-ART-BIBLE)</strong>: APPROVED [date] / CONCERNS (accepted) [date] / REVISED [date] | Iterations: [N]</p>
Per .ags/rules/review-workflow.md. Internal review runs in parallel with external Codex inside one loop. Each iteration:
.ags/project/reviews/.tmp/[type]-[slug]-iter[N]-draft.html./ags-external-review art-bible [draft-path] --embedded-parallel --iteration [N] --min-severity [floor] — Codex unavailable returns skipped: codex-unavailable; aggregator logs skip in decisions-log and continues with internal pool only.art-director) merges findings, drops nitpicks + below-floor.No iteration cap. No user-confirm gate before external. Record final iteration count for decisions-log entry written at skill completion.
On final approval:
<meta name="status" content="approved"> in <head>.<meta name="approved-at" content="YYYY-MM-DD"> to today.<span class="badge badge-draft">Draft</span> for <span class="badge badge-approved">Approved</span>..ags/project/decisions-log.md.Before presenting next steps, check project state:
design/gdd/systems-index.md exist? → map-systems done.ags/rules/technical-preferences.md contain configured engine? → setup-engine donedesign/gdd/ contain any *.md? → design-system has rundesign/gdd/gdd-cross-review-*.md exist? → review-all-gdds doneUse AskUserQuestion for next steps. Only include options genuinely next:
[_] /ags-map-systems — decompose concept into systems before writing GDDs (skip if systems-index.md exists)[_] /ags-setup-engine — configure engine (asset standards may need revisiting) (skip if engine configured)[_] /ags-design-system — start the first GDD (skip if any GDDs exist)[_] /ags-review-all-gdds — cross-GDD consistency check (skip if gdd-cross-review-*.md exists)[_] /ags-asset-spec — generate per-asset visual specs from approved GDDs (include if GDDs exist)[_] /ags-consistency-check — scan GDDs against art bible (include if GDDs exist)[_] /ags-create-architecture — author master architecture document[_] Stop hereAssign letters A, B, C… only to included options. Mark most logical pipeline-advancing option as (recommended). Always include /ags-create-architecture and Stop here.
Every creative-mode section: Brief → Agent draft (with consults in parallel) → Conflict surfacing → Approval → Write to file
data-agent (and data-consult if specified)<section ... data-*> tag attributes verbatim — they are the contract between template and skill.After art bible approved:
/ags-map-systems — decompose concept into game systems/ags-setup-engine — if engine not yet configured/ags-design-system [first-system] — start per-system GDDs/ags-consistency-check — validate GDDs against art bible/ags-create-architecture — produce master architecture document