迁移setup-engine工作流

skills/brainstorm/DETAILS.md

@@ -38,8 +38,8 @@ When this skill is invoked:
    - Do not add an explicit `Other` option in Codex app runs; the client supplies the
      free-form Other path. For app-server integrations, the equivalent free-form
      option is represented by `isOther`.
-   - If a Claude reference choice list has more than 3 options, split it into a
-     first 2-3 option category question plus a follow-up `request_user_input` call,
+   - If a choice list has more than 3 useful options, split it into a first
+     2-3 option category question plus a follow-up `request_user_input` call,
      or rely on the Codex free-form Other path for uncommon cases.
 
    Professional studio brainstorming principles to follow:
@@ -302,13 +302,13 @@ Ground the concept in reality:
 
 - **Target platform**: Use Codex `request_user_input` — "What platforms are you targeting for this game?"
   Options: `PC` / `Mobile` / `Console/Web`. Use the Codex free-form Other path for multiple platforms or a specific store target.
-  Record the answer — it directly shapes the engine recommendation and will be passed to `/setup-engine`.
+  Record the answer — it directly shapes the engine recommendation and will be passed to `$setup-engine`.
   Note platform implications if relevant (e.g., mobile means Unity is strongly preferred; console means Godot has limitations; web means Godot exports cleanly).
 
 - **Engine experience**: Use Codex `request_user_input` — "Do you already have an engine you work in?"
   Options: `Godot` / `Unity` / `Unreal`. Use the Codex free-form Other path for "No preference" or another engine.
   - If they pick an engine → record it as their preference and move on. Do NOT second-guess it.
-  - If "No preference" → tell them: "Run `/setup-engine` after this session — it will walk you through the full decision based on your concept and platform target." Do not make a recommendation here.
+  - If "No preference" → tell them: "Run `$setup-engine` after this session — it will walk you through the full decision based on your concept and platform target." Do not make a recommendation here.
 - **Art pipeline**: What's the art style and how labor-intensive is it?
 - **Content scope**: Estimate level/area count, item count, gameplay hours
 - **MVP definition**: What's the absolute minimum build that tests "is the
@@ -375,7 +375,7 @@ If yes, generate the document using the template at `../../references/studio-doc
    pre-production pipeline). List ALL steps — do not abbreviate or truncate:
 
 **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"
+   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)."
    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"
@@ -387,10 +387,10 @@ If yes, generate the document using the template at `../../references/studio-doc
    10. "Validate readiness to advance with `/gate-check` — phase gate before committing to production"
 
 **Path B — Prototype-First** (use if the core mechanic is unproven or the concept needs validation):
-   1. "Run `/setup-engine` to configure the engine"
+   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"
-   4. "If prototype PIVOTS: return to `/brainstorm` with the learnings and reshape the concept"
+   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"
 
 7. **Output a summary** with the chosen concept's elevator pitch, pillars,
@@ -414,7 +414,7 @@ append this notice to the current response before continuing:
 ## Recommended Next Steps
 
 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
+1. `$setup-engine` — configure the engine and populate version-aware reference docs
 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

skills/brainstorm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: brainstorm
-description: "Use when you need the /brainstorm game-production workflow. Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration."
+description: "Use when you need the /brainstorm or $brainstorm game-production workflow. Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration."
 ---
 
 # Brainstorm
@@ -15,10 +15,10 @@ the current project does not already have those agents installed in
 `python3 scripts/install_codex_runtime.py <target-project>` from the plugin root
 first.
 
-Review mode follows the Claude reference flow: `full` runs the `/brainstorm`
-director gates, `lean` skips those ordinary per-skill gates, and `solo` skips
-all director gates.
+Review mode follows Codex Game Studios gate settings: `full` runs the
+`$brainstorm` director gates, `lean` skips ordinary per-skill gates, and `solo`
+skips all director gates.
 
-`/brainstorm` writes `design/gdd/game-concept.md`. It defines and records game
+`$brainstorm` writes `design/gdd/game-concept.md`. It defines and records game
 pillars inside that concept document; it does not create
 `design/gdd/game-pillars.md` as a separate artifact.