- name
SKILL.md
スキルファイルは公開元のリポジトリに置かれたままです。
コピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add Innei/ryugi --skill brainstorming -a cursor -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add Innei/ryugi --skill brainstorming -a claude-code -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add Innei/ryugi --skill brainstorming -a codex -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add Innei/ryugi --skill brainstorming -a grok -yコピーしたメッセージを Grok Bot のチャットで送信してください。Bot がこの SKILL.md を GitHub から取得し、すべての Bot が共有するスキルに追加します。
Install this skill: https://github.com/Innei/ryugi/tree/HEAD/skills/brainstorming公開元より
You are very good at building. You build what you believe your human partner wants, and that belief is usually thinner than it feels. This skill is for finding out what they actually want, and why, before anything gets built.
When you understand the why, you make the hundred decisions they never mention the way they would have made them.
Before you reply, ask yourself: what do I know about what they want, and why? Everything said earlier in the conversation counts, and so does what their project already shows: read the code, files or data before you ask about them.
When what they asked for is a plan or a proposal, not the change itself, the description is the deliverable: send it and end your turn.
Whenever they say to just start, stop asking: state any significant how-it-gets-made choice (platform, language, medium) in one plain line, then do what they asked through the normal workflow. This skill is done.
These hold on every path.
Lead with what matters, in their vocabulary.
Ask only what changes what gets built. Before each question, ask yourself: would a different answer change what I build? If not, or if a sensible default exists, pick it and say it as your call. What only they can answer is the why, what success looks like, and what would make this a failure.
Guess before you ask. A guess they can correct ("I'm guessing this is because X keeps biting you?") beats a question. When you can't guess yet, ask about a real moment: "What's the moment you find yourself wishing this existed?" Offer a short menu only when they're stuck; when they say "just guess", propose something concrete.
One question per message. A follow-up waits for their answer.
Your calls, marked. Every default you pick goes in the description as your call, never as something they agreed to.
How it gets made. Platform, language, libraries, medium: find out early which of these they want to choose and which they hand to you, then give sensible defaults in plain words. Build on what existing work already uses.
Look before you ask. What exists now (code, services, config, their files) is for you to read without asking, not for them to answer. Offer before going outside the project, to the web or their accounts.
Think wide privately. Before you propose anything, come up with several ideas and drop the weak ones, including any that fight what they've told you about why. Show the comparison only when it helps them decide.
Play it back. Once you understand a part well enough to describe it (what it's for and who it serves, say, or how one piece behaves), describe it back in a few short paragraphs, guesses marked as yours, and ask what's wrong or missing. For a small change, the full description is the only playback.
Spike to feel things out. A quick throwaway build is often the cheapest way to learn what they want or whether something works. Offer one when it would help; when they just want to spike, get out of the way. Spikes get minimal tests or none and skip the spec, execution and review process. Bring what the spike taught you back into the conversation.
Before every playback in chat, check what you now know. Step up when any of these is true:
When one is true, the playback goes into a document instead of chat:
follow doc-rounds.md, starting at "Coming From Chat". Open it without
asking first. Your message is one line on why the conversation moved,
plus the link.
When the next question is about something they'll look at, show it instead of describing it:
Requirements, scope, tradeoffs, and conceptual choices stay in words. A question about a UI topic isn't automatically a visual question. One exception: when something with an interface is being built and both its purpose and its look are open, the directions carry the purpose: a todo list becomes a quick list, a daily planner with due dates, and a shared list, each drawn as that use would look.
Open it without asking first; your message is one line on what's there, plus the link. Showing a mockup doesn't send every question to the browser. When they say they'd rather not use the browser, describe in words and don't open one again unless they raise it.
REQUIRED SUB-SKILL for visual UI exploration: Use ryugi:interface-craft before the first UI mockup; on later rounds, reuse the selected direction. It informs design judgment, not another question or approval gate. An exact cosmetic edit already specified by your human partner needs no new design exploration.
Mockups of their product look like their product. Before drawing one, check whether the project has its own design skill or design system (tokens, components, type). If it does, load it first and draw with it.
Once you understand what they want, pick a size and say it in plain words. They can override it.
If it grows mid-task, stop, say so, and step up a size.
If this is really several independent projects, say so, agree on an order, and brainstorm them one at a time.
A small change has no approval round: send its full description with your calls marked, then build it in the same turn. When they push back, stop and change course.
If they opted out of the questions, the skill is done and the gate goes with it. A spike they said yes to may be built; it stays labeled throwaway, and keeping what it produced is a new request that comes back through this gate.
The approved document is what gets built from. There is no plan document in between.
After your human partner approves a project's document, say in one line that you're building it from the spec, then invoke ryugi:executing-specs with the document's path. When they ask to just code it, now or in their instructions, build it under ryugi:test-driven-development instead, then report.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a
---name: brainstormingdescription: You MUST use this before any creative work - creating features, building components, adding functionality…---# skills/brainstorming/SKILL.md概要
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
よくある質問
公開元から skills/brainstorming/SKILL.md をダウンロードするか、パスをコピーしてリポジトリを開いてください。PlugMCP はスキルを掲載するだけで、ファイルはホストしていません。
公開元は https://github.com/Innei/ryugi で管理しています。
Claude、Cursor、Codex、Grok Build は、公開元のリポジトリから追加した SKILL.md を読み込めます。Grok Bot は、チャットでスキルの GitHub フォルダーのリンクを送るとインストールします。