brainstorming
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese將想法集思廣益轉化為設計
Translating Brainstormed Ideas into Design
概述
Overview
通過自然的協作對話，幫助將想法轉化為完整的設計和規格。
首先了解當前的項目背景，然後一次提出一個問題來完善想法。一旦您瞭解了您正在構建的內容，就可以將設計分成小部分（200-300 個字），並在每個部分之後檢查到目前為止它看起來是否正確。
Help transform ideas into complete designs and specifications through natural collaborative dialogue.
First understand the current project background, then ask one question at a time to refine the idea. Once you understand what you're building, break the design into small sections (200-300 words) and check if it looks correct so far after each section.
流程
Process
理解這個想法：
- 首先檢查當前專案狀態（文件、文件、最近提交）
- 一次提出一個問題來完善想法
- 盡可能選擇多項選擇題，但開放式問題也可以
- 每個訊息只有一個問題 - 如果某個主題需要更多探索，請將其分解為多個問題
- 重點理解：目的、約束、成功標準
探索方法：
- 提出 2-3 種不同的權衡方法
- 透過對話方式提出選項以及您的建議和推理
- 以您推薦的選項開頭並解釋原因
展示設計：
- 一旦您相信自己瞭解了自己正在構建的內容，就可以展示設計
- 將其分成200-300字的部分
- 在每個部分之後詢問到目前為止看起來是否正確
- 涵蓋：架構、組件、數據流、錯誤處理、測試
- 如果有些事情沒有意義，準備回去澄清
Understanding the Idea:
- First check the current project status (documents, files, recent commits)
- Ask one question at a time to refine the idea
- Choose multiple-choice questions whenever possible, but open-ended questions are also acceptable
- Only one question per message - if a topic needs more exploration, break it into multiple questions
- Focus on understanding: purpose, constraints, success criteria
Exploring Approaches:
- Propose 2-3 different trade-off approaches
- Present options along with your recommendations and reasoning through dialogue
- Start with your recommended option and explain why
Presenting the Design:
- Once you're confident you understand what you're building, present the design
- Break it into sections of 200-300 words
- Ask if it looks correct so far after each section
- Cover: architecture, components, data flow, error handling, testing
- Be prepared to go back and clarify if something doesn't make sense
設計後
Post-Design
文件：
- 將經過驗證的設計寫入
docs/plans/YYYY-MM-DD-<topic>-design.md - 如果可以的話，使用風格元素：清晰簡潔的寫作技巧
- 將設計文檔提交到git
實施（如果繼續）：
- 問：“準備好實施了嗎？”
- 使用超能力：using-git-worktrees 創建隔離的工作區
- 使用超能力：寫作計劃制定詳細的實施計劃
Documentation:
- Write the validated design into
docs/plans/YYYY-MM-DD-<topic>-design.md - Use stylistic elements if possible: clear and concise writing techniques
- Commit the design document to git
Implementation (if proceeding):
- Ask: "Ready to implement?"
- Use superpower: using-git-worktrees to create isolated workspaces
- Use superpower: writing plans to develop a detailed implementation plan
關鍵原則
Key Principles
- 一次一個問題 - 不要因多個問題而不知所措
- 首選多項選擇 - 如果可能的話，比開放式更容易回答
- YAGNI 無情 - 從所有設計中刪除不必要的功能
- 探索替代方案 - 在解決之前始終提出 2-3 種方法
- 增量驗證 - 分部分展示設計，驗證每個部分
- 保持靈活性 - 當某些事情沒有意義時返回並澄清
- One Question at a Time - Don't overwhelm with multiple questions
- Prefer Multiple Choice - Easier to answer than open-ended when possible
- Relentless YAGNI - Remove unnecessary features from all designs
- Explore Alternatives - Always propose 2-3 approaches before settling
- Incremental Validation - Present the design in sections and validate each part
- Stay Flexible - Go back and clarify when something doesn't make sense