Back to Details

brainstorming

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Brainstorming Ideas Into Designs

从头脑风暴想法到设计

Overview

概述

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 in small sections (200-300 words), checking after each section whether it looks right so far.
通过自然的协作对话，帮助将想法转化为完整的设计方案与规格说明。
首先了解当前项目背景，然后逐个提出问题来完善想法。当你明确要构建的内容后，分小段（200-300字）呈现设计方案，每完成一段都要确认当前内容是否符合预期。

The Process

流程

Understanding the idea:
  • Check out the current project state first (files, docs, recent commits)
  • Ask questions one at a time to refine the idea
  • Prefer multiple choice questions when possible, but open-ended is fine too
  • 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 approaches with trade-offs
  • Present options conversationally with your recommendation and reasoning
  • Lead with your recommended option and explain why
Presenting the design:
  • Once you believe you understand what you're building, present the design
  • Break it into sections of 200-300 words
  • Ask after each section whether it looks right so far
  • Cover: architecture, components, data flow, error handling, testing
  • Be ready to go back and clarify if something doesn't make sense
理解想法：
  • 首先查看当前项目状态（文件、文档、最近的提交记录）
  • 逐个提出问题来完善想法
  • 尽可能采用选择题形式，开放式问题也可
  • 每条消息仅提出一个问题——若某个主题需要深入探讨，拆分为多个问题
  • 重点理解：目标用途、约束条件、成功标准
探索实现方案：
  • 提出2-3种不同的实现方案并说明各自的利弊
  • 以对话形式呈现选项，同时给出你的推荐方案及理由
  • 优先展示推荐方案并解释原因
呈现设计方案：
  • 当你明确要构建的内容后，开始呈现设计方案
  • 将内容拆分为200-300字的小段
  • 每完成一段都要确认当前内容是否符合预期
  • 涵盖：架构、组件、数据流、错误处理、测试
  • 若内容存在疑问，随时返回重新梳理

After the Design

设计完成后

Documentation:
  • Write the validated design to 
    docs/plans/YYYY-MM-DD-<topic>-design.md
  • Commit the design document to git
Implementation (if continuing):
  • Ask: "Ready to set up for implementation?"
  • Use 
    using-git-worktrees
    skill to create isolated workspace
  • Use 
    writing-plans skill
    to create detailed implementation plan
文档记录：
  • 将经过验证的设计方案写入 
    docs/plans/YYYY-MM-DD-<topic>-design.md
  • 将设计文档提交至 git
实现阶段（若继续推进）：
  • 询问：“是否准备好进入实现阶段？”
  • 使用 
    using-git-worktrees
    技能创建独立工作区
  • 使用 
    writing-plans skill
    制定详细的实现计划

Key Principles

核心原则

  • One question at a time - Don't overwhelm with multiple questions
  • Multiple choice preferred - Easier to answer than open-ended when possible
  • YAGNI ruthlessly - Remove unnecessary features from all designs
  • Explore alternatives - Always propose 2-3 approaches before settling
  • Incremental validation - Present design in sections, validate each
  • Be flexible - Go back and clarify when something doesn't make sense
  • 一次只提一个问题 - 避免同时提出多个问题造成困扰
  • 优先选择选择题 - 相较于开放式问题，选择题更易回答
  • 严格遵循YAGNI原则 - 从所有设计中剔除不必要的功能
  • 探索替代方案 - 在确定最终方案前，务必提出2-3种不同的实现思路
  • 增量式验证 - 分小段呈现设计，逐一验证
  • 保持灵活性 - 当内容存在疑问时，返回重新梳理