external/creative-writing-skills/cw-brainstorming/SKILL.md
Creative writing skill for capturing story brainstorming. Use when the user is exploring narrative ideas, discussing characters, planning episodes, or thinking through story possibilities. Creates minimal working notes that preserve creative freedom by recording only what was stated and marking sources.
npx skillsauth add seikaikyo/dash-skills cw-brainstormingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Capture story brainstorming in working note format that preserves creative freedom.
Record brainstorming WITHOUT:
AI suggestions are valuable but must be clearly marked and kept minimal.
This skill handles all brainstorming types:
All share core principles (minimal capture, source tagging, preserve vagueness). See references/ for specialized guidance:
chapter-planning.md - Capturing beat and scene explorationworldbuilding.md - Exploring fictional world elements (use web search for research)character-development.md - Exploring motivations, arcs, relationshipscontinuity-timeline.md - Timeline tracking and contradiction handlingRecord ONLY what the user explicitly states. Do NOT add elaborations, examples they didn't give, or details to fill gaps.
The problem is mixing, not suggesting:
❌ User: "Character A competes with B" → Capture: "A and B compete for leadership through a tournament with three rounds..." ✅ User: "Character A competes with B" → Capture: "A and B compete" + optional: "<AI>Tournament? Political? Trial?</AI>"
Default: Untagged = user said it. Most ideas come from the user, so treat them as the default.
ONLY use tags for special context:
<AI>...</AI> - AI suggestions/possibilities (MUST be clearly wrapped)
<AI>Competition could be: tournament-style, political maneuvering, or trial-based</AI><hidden>...</hidden> - Author-only information meant to be revealed later
<hidden>Z secretly wants them both to fail so he can reclaim leadership</hidden>When to offer AI suggestions:
When to stay minimal:
Keep it vague if user leaves it vague:
Working notes can contain contradictions and multiple possibilities. Don't resolve them - just list the options being considered.
Use whatever structure fits the discussion. Could be:
Essential elements:
<AI> tags<hidden> tags when relevantOptional sections based on discussion:
"I'm thinking character X and character Y compete for leadership. Maybe this creates tension with character Z who was the previous leader."
# Leadership Competition Notes
- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)
Open questions:
- Form of competition?
- How does Z respond?
- Outcome?
# Leadership Competition Arc
X and Y compete for leadership after Z steps down. Z feels threatened by the challenge to his authority.
The competition unfolds in three stages:
1. Announcement and initial positioning
2. First challenge where X demonstrates strength
3. Second challenge where Y shows wisdom
...
[20 more invented beats]
Why bad? Added massive elaboration the user never stated.
# Leadership Competition Notes
- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)
Open questions:
- Competition format: <AI>tournament-style? political maneuvering? trial-based?</AI>
- Z's response: <AI>oppose both? support one? stay neutral?</AI>
- Resolution?
# Leadership Competition Notes
- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)
- <hidden>Z is secretly manipulating both X and Y to destroy each other, planning to reclaim power after they're both discredited</hidden>
Open questions:
- Competition format?
- Outcome?
Why use <hidden>? The manipulation twist is planned for later reveal. Readers/characters don't know yet, but the author needs to track it while brainstorming.
Stop if you're writing:
Wrap AI suggestions in <AI> tags, keep minimal (2-3 options).
Good: User says "Yes, that's what I said" Bad: User says "I never said all that"
Notes should feel skeletal and incomplete. That's the point - preserves creative freedom.
DON'T just write notes and stop. After capturing, engage with the user to help develop ideas:
Useful follow-ups:
Keep it conversational:
The goal: Help the user think through their ideas, not take over the creative process.
Feel free to combine with other skills when helpful (e.g., using cw-official-docs to document finalized worldbuilding, or cw-story-critique to analyze what you're brainstorming).
brainstorm-[topic].mddevelopment
拋棄式 HTML mockup 比稿:產出 2 到 3 個設計立場不同的變體(密度 / 版式 / 強調軸,不是換色),各附取捨說明,最後給有立場的對比結論。適用:「畫個草圖」「比較 A 版 B 版」「先看方向再做」「給我看幾種做法」。要 production 元件或設計已定案時不適用。
tools
需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。
development
對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
testing
Reference for writing and editing agent skills well — the vocabulary and principles that make a skill predictable. Consult when authoring, reviewing, or pruning a SKILL.md.