brainstorm
When this skill is invoked:
-
Parse the argument for an optional genre/theme hint (e.g.,
roguelike,space survival,cozy farming). Ifopenor no argument, start from scratch. Also resolve the review mode (once, store for all gate spawns this run):- If
--review [full|lean|solo]was passed → use that - Else read
production/review-mode.txt→ use that value - Else → default to
lean
See
.claude/docs/director-gates.mdfor the full check pattern. - If
-
Check for existing concept work:
- Read
design/gdd/game-concept.mdif it exists (resume, don't restart) - Read
design/gdd/game-pillars.mdif it exists (build on established pillars)
- Read
-
Run through ideation phases interactively, asking the user questions at each phase. Do NOT generate everything silently — the goal is collaborative exploration where the AI acts as a creative facilitator, not a replacement for the human's vision.
More from donchitos/claude-code-game-studios
balance-check
Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
125playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
94team-narrative
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
92estimate
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.
81asset-audit
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
78design-review
Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
74