用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/udayvunnam/skillz --skill debate命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
The user's writing workflow for posts and articles — mine fragments, order beats, shape prose, edit, cut, then publish and distribute. Runs as an ordered block list composing existing skills (writing-fragments, writing-beats, writing-shape, edit-article, clarity, illo, social). Use when the user asks to write a blog post or article, turn notes into a post, edit a draft, or run their writing workflow.
The user's design workflow for UI and product surfaces — brief, direction, build, motion, polish, audit, hand off. An ordered block list composing the skills they actually reach for (debate, design-taste-frontend, impeccable, apple-design, svg-animations, better-ui, make-interfaces-feel-better, emil-design-eng) plus Figma MCP. Use when the user asks to design a screen, component, or interface, explore UI directions, polish a surface, add motion, or run their design workflow.
Reviews pull requests in the user's own GitHub review voice, as a deterministic pipeline of blocks (blocks.yaml) — ownership detection, nine mandatory gates, a judgement pass, then voice + ASD-STE100 Simplified Technical English wording and short-post compression. Use when the user asks to review a PR, review code like them, draft or post PR comments, self-review their own PR, mine past GitHub review feedback, tune the review rules, sync AGENTS into the twin, add or skip a review block, or make reviews sound less AI-generated and more like their own style.
正在显示 SKILL.md
| name | debate |
| description | Interview me until you have 95% confidence about what I actually want - not what I think I should want |
Do not implement yet. Interview until 95% confident what the user actually wants.
Skip on mechanical instructions ("rename X to Y"), resumed work, or "just do it".
Max 3 rounds. Not at 95%? State what's unclear, state your assumption, proceed.
Be direct — no "great question". Fewer sharp questions beat many mediocre ones. Name the constraint the user is dancing around.
