wxm/codex-game-studios
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

迁移art-bible到Codex原生skill

Browse Source
This commit is contained in:
wxm
2026-05-19 02:45:33 -07:00
parent 7c71d5dfde
commit f7b4fbed2a
13 changed files with 625 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
skills/brainstorm/DETAILS.md
View File

@@ -379,7 +379,7 @@ If yes, generate the document using the template at `../../references/studio-doc
**Path A — Design-First** (recommended if the concept is well-defined):
1. "Run `$setup-engine` to configure the engine and populate version-aware reference docs"
2. "Run `/art-bible` to create the visual identity specification — do this BEFORE writing GDDs. **The art bible is required before the Technical Setup gate.** It gates asset production and shapes technical architecture decisions (rendering, VFX, UI systems)."
2. "Run `$art-bible` to create the visual identity specification — do this BEFORE writing GDDs. **The art bible is required before the Technical Setup gate.** It gates asset production and shapes technical architecture decisions (rendering, VFX, UI systems)."
3. "Use `/design-review design/gdd/game-concept.md` to validate concept completeness before going downstream"
4. "Discuss vision with the `creative-director` custom agent for pillar refinement"
5. "Decompose the concept into individual systems with `/map-systems` — maps dependencies, assigns priorities, and creates the systems index"
@@ -392,7 +392,7 @@ If yes, generate the document using the template at `../../references/studio-doc
**Path B — Prototype-First** (use if the core mechanic is unproven or the concept needs validation):
1. "Run `$setup-engine` to configure the engine"
2. "Run `/prototype [core-mechanic]` — validate the core idea is fun before writing any GDDs (1–3 days throwaway code)"
3. "If prototype PROCEEDS: run `/art-bible`, then continue with Path A steps 5–10 above, using prototype learnings to inform your GDDs"
3. "If prototype PROCEEDS: run `$art-bible`, then continue with Path A steps 5–10 above, using prototype learnings to inform your GDDs"
4. "If prototype PIVOTS: return to `$brainstorm` with the learnings and reshape the concept"
5. "After full design and architecture, build the `/vertical-slice` to validate production readiness before committing to sprints"
@@ -418,7 +418,7 @@ append this notice to the current response before continuing:
After the game concept is written, follow the pre-production pipeline in order:
1. `$setup-engine` — configure the engine and populate version-aware reference docs
2. `/art-bible` — establish visual identity before writing any GDDs
2. `$art-bible` — establish visual identity before writing any GDDs
3. `/map-systems` — decompose the concept into individual systems with dependencies
4. `/design-system [first-system]` — author per-system GDDs in dependency order
5. `/create-architecture` — produce the master architecture blueprint