show-dont-tell
仓库创建 2026年7月28日最近提交 1 天前SkillHot 收录 1 天前
▸ 精选理由
强制结构化思考，便于评审和快速否决方案细节。
这个 Skill 做什么
将计划/设计以图表为主输出，使用mermaid代替大段文字说明。
把计划、设计或流程用图先说清楚，输出以 mermaid 图为主、短文跟随解释，避免长篇大论。在做方案评审、写 RFC、回答“怎么建/修/迁移 X”或任何三步以上流程时就该用。特点是图迫使你把流程顺序、分支和失败路径说清楚，阅读者也能更快定位问题。
▸ 展开 SKILL.md 英文原文
Show, don't tell — plans, specs, and approvals ship as mermaid diagrams, never walls of text, because a picture is worth a thousand words. Trigger whenever you present a plan for approval, write or review a plan, spec, design doc, architecture proposal, or RFC, answer 'how should we build/fix/migrate X', or explain any workflow with three or more steps — the diagram leads, a short prose chaser follows. If you're about to write paragraphs describing steps, load this first. When in doubt, trigger.
0
Stars
0
Forks
2
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话（通用）
帮我安装这个 skill：https://raw.githubusercontent.com/MarcPelberg/skills/main/show-dont-tell/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/MarcPelberg/skills/main/show-dont-tell/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# Show, Don't Tell One rule: when the content is a plan, a design, or a process, the diagram is the deliverable. A diagram forces you to commit to order, branches, and failure paths that prose lets you mumble through — and the reader can veto a box faster than they can veto a paragraph. That's why the diagram leads and the prose chases. ## When a diagram is mandatory - Presenting a plan for approval (whatever the runtime calls that step — the plan itself IS the diagram). - Writing or reviewing a plan, spec, design doc, architecture proposal, or RFC. - Answering "how should we build/fix/migrate X". - Explaining any workflow, pipeline, or process with three or more steps. Litmus test: if
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有