art-bible

To create an art bible, author a sectioned document defining the game's visual identity, color system, shape language, character and environment direction, UI visual language, asset standards, and curated references. This skill generates a written art-bible.md file ready for production.

A game art bible should include nine canonical sections: visual identity, mood, shape language, color system, character direction, environment direction, UI visual language, asset standards, and references. The skill authors or retrofits these sections based on existing design content.

To update an existing art bible, the skill performs context checks against design and game design document content, identifies missing or placeholder sections, and only updates those specific areas while preserving existing approved content.

Yes, you can define concrete asset standards, naming conventions, texture and LOD budgets, and colorblind accessibility rules within the art bible. These constraints integrate with technical-preferences and engine constraints for production readiness.

Art direction coordination uses agent delegation to spawn art-director, technical-artist, ux-designer, and creative-director tasks for each art bible section. Director gate outcomes are recorded to manage approval flows and sign-off.

Yes, an approved game concept and reference materials are required before authoring an art bible. The skill uses the approved brainstorm output and reference materials to produce a usable art-bible.md that an outsourcing team can follow without additional briefing.