design-doc
把需求转成可执行的技术设计，便于开发与评审落地实施。
为功能或系统生成可执行的 DESIGN.md 技术设计文档与实现细节。
把功能或系统的技术实现写成完整的 DESIGN.md，说明要建哪些组件、数据如何流动、要暴露哪些 API，以及选型和取舍理由。在 PRD 写好需求、准备开发前使用，把高层需求变成可执行的实现计划。特点是既有模块划分又有实现细节，方便工程师按文档落地。
▸ 展开 SKILL.md 英文原文
Generate a complete DESIGN.md file for any software project. Use whenever the user asks to create, write, generate, or draft a DESIGN.md — a technical design document that explains HOW a system will be built. Also use when the user says they want a "system design doc", "technical design spec", "implementation plan", or "how are we building this". This skill triggers AFTER a PRD exists (what and why) and BEFORE implementation begins. The DESIGN.md answers: what components, what data flow, what APIs, what tech choices, and why those choices. Do NOT trigger for UI/visual design (use design-system skills), or for editing existing DESIGN.md files (use file tools directly), or for architecture decisions (use Architecture.md skill).
帮我安装这个 skill：https://raw.githubusercontent.com/arsudsandesh97/Revoact/main/skills/design-doc/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/arsudsandesh97/Revoact/main/skills/design-doc/SKILL.md"# DESIGN.md Author Skill You are a technical design writer. Your job is to create a `DESIGN.md` file that explains the technical approach for implementing a feature or system. ## Philosophy A DESIGN.md is the bridge between "what we're building" (PRD) and "the code itself" (implementation). It answers: - **What components/modules** will we build? - **How do they interact?** (data flow, APIs, events) - **What technologies** are we using and why? - **What are the trade-offs** in our approach? The audience is **engineers on your team** who need to understand the system before writing code. It should be detailed enough that someone could implement it, but not prescriptive about every line of