brainstorm

brainstorm is a skill for Claude Code from IdoCohen560/claude-unity-game-studio. It costs 36 tokens per session (4,525 once invoked), scanned A, a copy of brainstorm, MIT.

A guided skill for developing a game concept from an initial idea into a structured design document. It uses creative exercises and asks questions about genre, theme, players, scope, and direction.

In plain words
What is it for?
Use it to explore game ideas, compare possible concepts, define design pillars, and build or continue a game concept document.
Why use it?
It helps turn an unfinished idea into a clearer concept through interactive decisions rather than generating the entire design without user input.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Good fit Use it to explore game ideas, compare possible concepts, define design pillars, and build or continue a game concept document.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/idocohen560/claude-unity-game-studio/brainstorm
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add IdoCohen560/claude-unity-game-studio --skill brainstorm
Clone the repo
git clone --depth 1 https://github.com/IdoCohen560/claude-unity-game-studio

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for brainstorm

README.md
[![agentmods](https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/brainstorm/github.svg)](https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/brainstorm)
Your own site
<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/brainstorm"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/brainstorm/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for brainstorm

Your own site · 80×15
<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/brainstorm"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/brainstorm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,525 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.04525
Opus 5 $0.00018 $0.02263
Sonnet 5 $0.00007 $0.00905
Haiku 4.5 $0.00004 $0.00453

Measured 9d ago against content hash 344fc4a3c040, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

brainstorm scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

83% identical to brainstorm — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

examples/my-first-game/.claude/skills/brainstorm/SKILL.md · 351 lines

How it starts

The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When this skill is invoked:

  1. Parse the argument for an optional genre/theme hint (e.g., roguelike, space survival, cozy farming). If open or no argument, start from scratch. Also resolve the review mode (once, store for all gate spawns this run):

    1. If --review [full|lean|solo] was passed → use that
    2. Else read production/review-mode.txt → use that value
    3. Else → default to lean

    See .claude/docs/director-gates.md for the full check pattern.

  2. Check for existing concept work:

    • Read design/gdd/game-concept.md if it exists (resume, don't restart)
    • Read design/gdd/game-pillars.md if it exists (build on established pillars)
  3. 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.

    Use AskUserQuestion at key decision points throughout brainstorming:

    • Constrained taste questions (genre preferences, scope, team size)
    • Concept selection ("Which 2-3 concepts resonate?") after presenting options
    • Direction choices ("Develop further, explore more, or prototype?")
    • Pillar ranking after concepts are refined Write full creative analysis in conversation text first, then use AskUserQuestion to capture the decision with concise labels.

    Professional studio brainstorming principles to follow:

    • Withhold judgment — no idea is bad during exploration
    • Encourage unusual ideas — outside-the-box thinking sparks better concepts
    • Build on each other — "yes, and..." responses, not "but..."
    • Use constraints as creative fuel — limitations often produce the best ideas
    • Time-box each phase — keep momentum, don't over-deliberate early

Phase 1: Creative Discovery

Start by understanding the person, not the game. Ask these questions conversationally (not as a checklist):

Emotional anchors:

  • What's a moment in a game that genuinely moved you, thrilled you, or made you lose track of time? What specifically created that feeling?
  • Is there a fantasy or power trip you've always wanted in a game but never quite found?

Taste profile:

  • What 3 games have you spent the most time with? What kept you coming back? (Ask this as plain text — the user must be able to type specific game names freely. Do NOT put this in an AskUserQuestion with preset options.)
  • Are there genres you love? Genres you avoid? Why?
  • Do you prefer games that challenge you, relax you, tell you stories, or let you express yourself? (Use AskUserQuestion for this — constrained choice.)

Practical constraints (shape the sandbox before brainstorming). Bundle these into a single multi-tab AskUserQuestion with these exact tab labels:

  • Tab "Experience" — "What kind of experience do you most want players to have?" (Challenge & Mastery / Story & Discovery / Expression & Creativity / Relaxation & Flow)
  • Tab "Timeline" — "What's your realistic development timeline?" (Weeks / Months / 1-2 years / Multi-year)
  • Tab "Dev level" — "Where are you in your dev journey?" (First game / Shipped before / Professional background)

Use exactly these tab names — do not rename or duplicate them.

Synthesize the answers into a Creative Brief — a 3-5 sentence summary of the person's emotional goals, taste profile, and constraints. Read the brief back and confirm it captures their intent.


Read the full file on GitHub · 351 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 351 lines · 36 tokens per session scan A 344fc4a3c040

Subscribe to this mod's changes

brainstorm is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (18 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 4,525 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to brainstorm, differing in 27 lines, and is treated as a copy.

Related

Other skills, from other repositories

swarm

Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…

Zintellix/Claude-Skills · 138 tokens

memory-loop-setup

Bootstrap the memory loop into any repo or Obsidian vault. Triggers: (1) "set up the memory loop / second brain / warm layer here" or "install this structure in another repo/vault", (2) a new project asking "make the AI remember across sessions and surfaces".

Elliotoh-jin/claude-memory-loop · 66 tokens

discord-intent-application

Helps write the justification text for Discord Developer Portal privileged intent applications (Message Content, Server Members, Presence) for a specific bot. Takes a plain-text description of the bot's functionality and/or an uploaded/local codebase, screens the bot's features against Discord's known rejection…

The-LukeZ/discord-intent-application · 144 tokens

plan-qa

Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA- - .md) that /execute-qa…

foyzulkarim/skills · 110 tokens

execute-qa

Executes a QA specification (specs/qa/QA- - .md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact…

foyzulkarim/skills · 106 tokens

generate-tasks

Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS- - .md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.

foyzulkarim/skills · 74 tokens