菜单
Use when writing or rewriting DESIGN.md for a software project from sparse product intent, especially when the document should name implementation concepts, define components, and stay concise.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | design-doc-writer |
| description | Use when writing or rewriting DESIGN.md for a software project from sparse product intent, especially when the document should name implementation concepts, define components, and stay concise. |
Read repository instructions and the existing DESIGN.md before editing.
Treat the first pass as a reader review: check structure, ordering, prose
quality, redundancy, and missing implementation concepts.
Define the project first in one or two paragraphs. State what the system does, then name the main transformation or design idea.
Organize the document by concepts and components. Give each concept a stable name, a short definition, and the rules needed to implement it.
Prefer declarative prose. Each paragraph should introduce one concept, state its properties, and stop.
Specify ownership, data flow, lifecycle, sizing, and failure behavior when they affect implementation.
After editing, reread the document as a reader. Remove policy-like filler, redundant sections, and vague statements. Tighten any sentence that does not help implementation.
