brainstorming
設計協作腦力激盪
也可從以下取得: Cycleaddict,Cygnusfear,obra,davila7,DMJGilbert,DYAI2025,ArieGoldkin,CodingCossack
此技能協助 AI 助手透過結構化對話將模糊的想法轉化為具體設計，確保在開始實作前需求清晰明確。
下載技能 ZIP
在 Claude 中上傳
前往 設定 → 功能 → 技能 → 上傳技能
開啟並開始使用
測試它
正在使用「brainstorming」。 I want to add a user notification system to my app
預期結果:
Great! Let me understand what you are building. First question: What is the primary purpose of these notifications - are they for user activity (like comments, likes), system alerts (maintenance, errors), or something else?
正在使用「brainstorming」。 What if I want push notifications too?
預期結果:
Good point. I have two approaches to consider:
1. **Single channel first**: Start with in-app notifications, add push later when you have more resources.
2. **Multi-channel from start**: Use a service like OneSignal or Firebase that handles both.
My recommendation is approach 1 if you are early stage - it keeps complexity down. Which direction interests you more?
安全審計
安全Static analysis flagged external commands and cryptographic algorithms, but manual review confirms these are false positives. The skill contains only documentation text - no executable code. Backticks at line 38 are markdown formatting, not shell execution. No cryptographic code exists in the skill.
高風險問題 (1)
中風險問題 (1)
品質評分
你能建構什麼
新功能規劃
當使用者想要新增功能時，引導他們在開始任何實作前先了解需求、限制條件和成功標準。
元件設計會議
透過提出針對性問題、呈現選項並透過對話迭代設計，協助設計新的 UI 元件或後端服務。
架構探索
探索系統的不同架構方法，呈現權衡與建議，同時在每個步驟驗證理解。
試試這些提示
I want to build something new. Can you help me brainstorm the design? The idea is: [describe your idea]. What questions do you have to understand what I am building?
We are designing [feature/system]. Based on what we discussed, what approaches would you recommend? Please present 2-3 options with trade-offs.
Here is my proposed design for [section]: [design content]. Does this look right? What should I clarify or change?
We have validated the design. Can you write this up as a design document at docs/plans/[topic]-design.md?
最佳實務
- 每則訊息只問一個問題，避免讓使用者不知所措
- 盡可能使用選擇題以獲得更快的回應
- 先提出你的建議，然後解釋理由
- 透過呈現設計部分來增量驗證理解
避免
- 在單一訊息中提出多個問題
- 未先驗證設計就跳到實作
- 僅呈現一個選項而未探索替代方案
- 忽略使用者回饋並繼續執行原始計劃