designlisted

# Brainstorming Ideas Into Designs **Speak the repository's language.** The first script this skill runs — `<cue>/gate`, or `<cue>/init-check` — prints a `language` line. **Everything you say to the user goes in that language, starting with your first sentence**: the questions you ask, not only the record you write at the end. This skill body is English because it is the plugin's source, not because it is your output. Template headings, commit markers, `outcome.md` status tokens, paths and code stay exactly as written. Help turn ideas into fully formed designs and specs through natural collaborative dialogue. Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval. <HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity. </HARD-GATE> ## Prerequisite check **Run this first, before reading anything.** It settles in one call whether this stage may run here, against which KEY, and — if it may not — what is available instead. ``` <cue>/gate design ``` `<cue>` is the scripts directory named in your session context. Substitute that path and nothing else — a Windows path assembled by hand produces `d:cuepluginscue-devscriptsgate: command not found`, wh