Art Bible

Purpose

An art bible is the canonical reference for every visual decision in a game project. It defines the art style (cel-shaded, pixel art, photorealistic, stylized PBR), the color palettes for environments and characters, character proportion guides and silhouette standards, environment mood boards with lighting direction, material and shader specifications, asset naming conventions, and the production constraints (polygon budgets, texture resolution tiers, draw-call targets) that every artist works within.

Without an art bible, visual consistency degrades silently. One environment artist interprets “fantasy forest” as saturated Ghibli watercolor; another builds dark, desaturated realism. A character modeler uses 40K triangles where the budget allows 15K. Outsourced assets arrive in the wrong color space or with non-standard UV layouts. These inconsistencies compound: by the time the art director notices, dozens of assets need rework. The cost of rework scales with production—retexturing a single character set can consume a full sprint.

The art bible prevents this by making visual intent explicit and verifiable. It is not a mood board collection or a Pinterest link dump. It is a production specification: precise enough that an artist joining the project mid-cycle can produce on-brand assets without asking for clarification, and specific enough that an automated pipeline can validate asset compliance against documented constraints.

Who needs this document

What separates a good version from a bad one

Criterion 1: Art style is defined with visual references and explicit constraints

✓ Strong: “Art style: stylized PBR with hand-painted texture overlays. Base palette limited to 5 hues per biome (desert: amber, burnt sienna, ivory, slate blue, sage). Character outlines: 2px screen-space edge detection shader, color sampled from darkest albedo value. Reference artists: Arcane (Fortiche), Hades (Supergiant). Anti-references: photorealism, anime proportions.”

✗ Weak: “The game should have a stylized look, colorful but not too cartoony.” (Every artist will interpret “stylized” and “not too cartoony” differently. Without palette constraints, reference artists, and anti-references, the art direction exists only in the art director’s head.)

Criterion 2: Character and prop specifications include measurable production constraints

✓ Strong: “Player character: 12K–15K triangles, 2048×2048 albedo + normal + mask map (RGB: metallic, roughness, AO). NPCs tier 1 (quest-givers): 8K–10K triangles, 1024×1024 textures. NPCs tier 2 (crowd): 3K triangles, 512×512 shared atlas (max 16 per atlas page). All characters rigged to standard skeleton v2.3 (68 bones). Silhouette test: every playable character must be identifiable at 50% screen zoom on a solid background.”

✗ Weak: “Characters should be detailed but optimized for performance.” (No triangle budget, no texture resolution, no skeleton standard. “Detailed but optimized” is a contradiction without numbers—it tells the artist nothing actionable.)

Criterion 3: Asset naming and directory conventions are machine-parseable

✓ Strong: “Asset naming: {category}_{name}_{variant}_{resolution}.{ext}. Example: prop_barrel_broken_1k.fbx. Categories: char, prop, env, vfx, ui. Directory structure: Assets/Art/{Category}/{Biome}/{AssetName}/. Texture suffixes: _albedo, _normal, _mask, _emissive. All lowercase, underscores only, no spaces or special characters.”

✗ Weak: “Use descriptive names for assets and keep them organized in folders.” (Without a naming schema, artists invent their own conventions. Automated import scripts, LOD generators, and texture streaming systems all depend on predictable naming patterns.)

Criterion 4: Color palettes and lighting are specified with numerical values

✓ Strong: “Global palette: defined in palette.ase (Adobe Swatch Exchange), committed to repository. Key light: warm directional (color temp 5500K, intensity 1.2, 35° elevation, 220° azimuth). Fill light: cool ambient (color temp 7500K, intensity 0.3). Rim light: accent color sampled from biome secondary hue, intensity 0.6. Fog: exponential height fog, base density 0.02, falloff 0.8, inscattering color matches sky gradient at horizon.”

✗ Weak: “Lighting should feel warm and inviting during the day, cool and mysterious at night.” (Subjective descriptions produce subjective results. Without color temperatures, intensities, and fog parameters, every level artist will produce a different lighting setup.)

Common mistakes

Mood boards without specifications. The art bible contains 30 pages of reference images with no written constraints, polygon budgets, or palette definitions. Artists study the mood boards and each extracts a different interpretation. Pair every reference image with the specific properties it illustrates and the measurable constraints that apply.

Ignoring technical constraints. The art bible specifies beautiful 4K textures and 50K-triangle characters without consulting the rendering budget. Assets are built, then half must be rebuilt when performance targets are missed. Collaborate with engineering to set polygon, draw-call, and VRAM budgets before defining asset tiers.

No anti-references. The art bible says what the game should look like but never what it should not look like. Without anti-references, artists drift toward familiar styles that conflict with the intended direction. Include 3–5 explicit anti-references with explanations of what to avoid and why.

Treating the art bible as a one-time artifact. The art bible is written during pre-production and never updated. By mid-production, the actual art has evolved beyond the original document. Designate a living section with a changelog, and update it when style decisions change—every artist should work from the current version, not the launch-day snapshot.

No validation pipeline. The art bible defines naming conventions and polygon budgets, but nothing in the build pipeline enforces them. Non-compliant assets accumulate until someone manually audits. Implement automated checks (naming regex, triangle count limits, texture resolution validation) as part of the asset import pipeline.

How to use this document

When to create it

Create the art bible during pre-production, after the game design document establishes the game’s genre, setting, and tone, but before any production art is created. The art bible should be the first deliverable of the art direction phase. If concept art already exists, the art bible codifies the decisions those concepts represent—it is not a post-hoc rationalization but a forward-looking production specification. Update it at each major milestone (vertical slice, alpha, beta) to reflect evolved decisions.

Who owns it

The art director or lead artist owns the art bible. On small teams without a dedicated art director, the person making the most visual decisions owns it. Technical artists should co-author the sections on shader standards, polygon budgets, and naming conventions, since these sections must align with the rendering pipeline. Any change to visual direction must be reflected in the art bible before new assets are produced against it.

How AI agents should reference it

get_standard_docs(type="video_game", features=["3d_graphics"])
→ art_bible in documents[]
→ agent reads art bible before generating any visual asset specifications
→ agent applies documented naming conventions: {category}_{name}_{variant}_{resolution}
→ agent enforces polygon budgets per asset tier when generating import scripts
→ agent references palette.ase path for color validation in shader code

The prompt_snippet — “Ensure the project has an art bible defining visual style, color palette, character design guidelines, and asset production standards” — tells the agent to verify that all four dimensions are present with specific, measurable values rather than subjective descriptions.

How it connects to other documents

The Art Bible is downstream of the Game Design Document, which establishes the setting, tone, and genre that the visual style must serve. It feeds the UI Style Guide (which inherits palette and typography from the art bible), the Asset Pipeline Specification (which implements the naming conventions, resolution tiers, and validation rules the art bible defines), and Brand Guidelines (which extend the game’s visual identity to marketing materials, store pages, and merchandise). Changes to the art bible ripple into all four of these documents.

Recommended Reading

• The Art of Game Design by Jesse Schell — Covers the intersection of aesthetics and design intent; essential context for why visual decisions must serve gameplay.
• Real-Time Rendering by Tomas Akenine-Möller, Eric Haines & Naty Hoffman — The technical foundation for understanding polygon budgets, shader pipelines, and rendering constraints that art bibles must respect.
• Color and Light: A Guide for the Realist Painter by James Gurney — Practical color theory and lighting principles directly applicable to defining palettes and lighting specifications in an art bible.
• The Animator’s Survival Kit by Richard Williams — While focused on animation, the chapters on silhouette, proportion, and visual clarity inform character design guidelines in any art bible.