unikit-gd-brainstorm

# Game Design — Concept Brainstorming Generate game ideas with the user and crystallize the chosen one into a **CONCEPT card** at `.unikit/gamedesign/concepts/<date>_<slug>/CONCEPT.md`, with the rejected ideas parked in `IDEAS.md`. This is the **ideation** front of the design pipeline — it produces concepts; `unikit-gd-spec` turns a concept into `GAME.md` and a system map. This skill **generates new ideas**. Analyzing an existing game or market (reference dissection, trade-off tables) is `unikit-gd-explore`. The distinguishing test: *five concept cards → brainstorm; a comparison table → explore.* ## Language Awareness — BLOCKING PRE-REQUISITE **BEFORE producing ANY output**, silently read `.unikit/system/LANGUAGE_RULES.md` and apply it to all output and artifacts (fall back to English if it is missing) — including the rule to **translate concepts, not transliterate jargon**. `gd-principles` → "Language" adds the game-design specifics: which IDs and stored field values (e.g. `market_signal: red-ocean`) stay English. Do not announce the language setting. ## Bootstrap (MANDATORY) Before responding, silently load — do not narrate: 1. **`.unikit/system/gamedesign/gd-principles.md`** (the core) — the collaborative protocol (Question → Options → Decision → Draft → Approval, Explain → Capture), the "never guess" rule, anti-anchoring, the language rules. This skill **applies** it. If missing, warn (`unikit-ai update`) and continue with the protocol summarized above....