mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
Fix release for 1.1.1: the minimal path end to end, engine commands that run on Godot, Unity and Unreal, hook warnings you can see, and verdicts that say when they could not check. Details in CHANGELOG.md; upgrade steps in UPGRADING.md (v1.1.1 → v1.1.2). Fixes #67 Fixes #131 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuJn2FdynEybfL5KC697nJ
27 lines
1.6 KiB
Markdown
27 lines
1.6 KiB
Markdown
> Gate definition. The spawning skill passes this file's path to the director agent; the AGENT reads it — the parent session should not.
|
|
|
|
# AD-ART-BIBLE — Art Bible Sign-Off
|
|
|
|
Agent: `art-director` | Model tier: session (inherit) | Domain: Visual identity, art bible, visual production readiness
|
|
|
|
**Trigger**: After the art bible is drafted (`/art-bible`), before asset production begins
|
|
|
|
**Context to pass**:
|
|
- Art bible path (`design/art/art-bible.md`)
|
|
- Game pillars and core fantasy
|
|
- Platform and performance constraints (`platform.*` and `performance.*` from `project.yaml`, falling back to `.claude/docs/technical-preferences.md`)
|
|
- Visual identity anchor chosen during brainstorm (from `design/gdd/game-concept.md`; if there is no `design/gdd/game-concept.md`, pass the "Art & audio direction" line of `design/game-brief.md` instead)
|
|
|
|
**Prompt**:
|
|
> "Review this art bible for completeness and internal consistency. Does the color
|
|
> system match the mood targets? Does the shape language follow from the visual
|
|
> identity statement? Are the asset standards achievable within the platform
|
|
> constraints? Does the character design direction give artists enough to work from
|
|
> without over-specifying? Are there contradictions between sections? Would an
|
|
> outsourcing team be able to produce assets from this document without additional
|
|
> briefing? Return APPROVE (art bible is production-ready), CONCERNS [specific
|
|
> sections needing clarification], or REJECT [fundamental inconsistencies that must
|
|
> be resolved before asset production begins]."
|
|
|
|
**Verdicts**: APPROVE / CONCERNS / REJECT
|