Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/brainstorm
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.
Passed 18 of 22 test cases with the skill, and 5 of 22 without it.
and 21 more in the full report
13 fixed5 passed either way4 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
During a multi-phase brainstorming session, at what context window usage percentage must the skill display a context limit warning message to the user, and what file location does it reference?
| Checked | Without skill | With skill |
|---|---|---|
| Append context warning notice when context usage reaches 70 percent | Missed | Passed |
| Specify design/gdd/game-concept.md as saved file in context warning notice | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,docs.density,workflow
Resolved above — use as-is. No block → defaults in
.claude/docs/config-resolution.md.
--review overrides review_mode; store it for all gate spawns this run. See
.claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md — the spawned agent reads its own gate file; do not read it in the parent session.
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
docs.density — it controls per-section depth, where workflow
controls which sections exist. modes.rigor sets both together; set
docs.density explicitly to vary depth alone: terse (the default, via rigor: minimal) = pillar bullets + concept bullets;
balanced = pillars + concept with brief rationale (rigor: standard); thorough =
pillars + concept + extensive rationale + alternatives. Apply it to every section
you author.
workflow FIRSTThe workflow tier resolved above governs this skill's output:
standard / full → run the full flow ("When this skill is invoked" through
Phase 5 and the concept-document generation). No change.minimal → run the Lean Brief flow immediately below and STOP — skip
Phases 1–5, the director gates (CD-PILLARS / AD-CONCEPT-VISUAL / TD-FEASIBILITY /
PR-SCOPE), and the full-length concept document entirely. Output is the one-page
design/game-brief.md, not game-concept.md.workflow: minimal only)A jam / small-scope session: capture the load-bearing thinking in one page, then get
to code. Keep prompting light — a few exchanges, not fifteen. Author from the
one-page template .claude/docs/templates/game-brief.md (6 required fields + 3
test cases passed, vs 5 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.