art-bible

Generate nine-section Art Bible documents from approved game concepts.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill art-bible-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: art-bible
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/art-bible
Command: npx skills add https://github.com/WindXRan/y3td --skill art-bible-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It standardizes and de-risks game art production by creating a single, section-by-section Art Bible that establishes visual identity and production rules before GDD, systems, or assets begin.

Core Features & Use Cases

  • Guided, section-by-section authoring: Produces nine structured sections (visual identity, mood/atmosphere, shape language, color system, character/environment/UI direction, asset standards, and prohibitions) with approvals after each section draft.
  • Retrofit-safe workflow: Detects an existing art-bible file and only fills empty or placeholder sections without overwriting complete content.
  • Production-grade constraints with agent delegation: Coordinates art-director (and parallel roles like ux-designer and technical-artist where needed) to translate design pillars into actionable constraints, while explicitly surfacing conflicts for user decisions.

Quick Start

Run art-bible in lean mode by asking the AI to execute: art-bible --review lean.

Frequently Asked Questions about art-bible

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an art bible for game asset production?

An art bible standardizes game art production by establishing a single document detailing visual identity, shape language, and asset standards. It acts as a mandatory gate to de-risk visual consistency before any GDD systems writing or asset creation begins.

When do I need an art bible before starting GDD system writing?

You need an art bible before GDD system writing to enforce production-grade constraints and translate design pillars into actionable visual rules. This gated handoff workflow de-risks asset creation by surfacing art-direction conflicts early.

How do I retrofit existing art direction documents without overwriting content?

To retrofit existing art direction documents safely, use a review-mode parsing workflow that detects existing art-bible file completeness. It only drafts empty or placeholder sections, preserving your complete content without overwriting.

What sections are required for a complete game art direction document?

A complete game art direction document requires nine sections: visual identity, mood/atmosphere, shape language, color system, character direction, environment direction, UI direction, asset standards, and prohibitions, each requiring user sign-off.

Can I use agent delegation to draft specific sections like UI direction?

Yes, you can use agent delegation to draft sections like UI direction by coordinating parallel roles such as ux-designer and technical-artist. This translates design pillars into actionable constraints while explicitly surfacing conflicts for user decisions.

Does art-bible work for lean review workflows?

Yes, art-bible works for lean review workflows by executing a lean mode command. This initiates a guided, section-by-section authoring process that applies production-grade constraints with immediate file writing and delegated drafting.