设计规则
- 作者仓库星标 43
- 作者仓库 claude-kit
- 领域
- 设计与多媒体
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @hex0xdeadbeef · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步:在 /designer 启动时加载
阅读此 SKILL.md 了解概述。支持每阶段按需加载文件。
步骤 2:使用相位驱动加载
第 3 阶段(建议)→ 阅读规格质量以了解方法评估标准第 4 阶段(写入规范)→ 阅读设计检查表以进行自我验证第 5 阶段(用户门)→ 在呈现给用户之前验证检查表
# Design Rules
## Purpose
Guidelines for the /designer command to produce high-quality design specs that reduce plan-review iterations.
## Instructions
### Step 1: Load at /designer startup
Read this SKILL.md for overview. Supporting files loaded on-demand per phase.
### Step 2: Use phase-driven loading
- Phase 3 (PROPOSE) → read [Spec Quality](spec-quality.md) for approach evaluation criteria
- Phase 4 (WRITE SPEC) → read [Design Checklist](design-checklist.md) for self-verification
- Phase 5 (USER GATE) → verify checklist before presenting to user
## Spec Quality Criteria
| Criterion | Required | Check |
|-----------|----------|-------|
| Context describes current state | Yes | Not just "add X" but "currently Y exists, need X because Z" |
| Scope has IN and OUT | Yes | OUT items have explicit reasons |
| At least 2 approaches compared | Yes | With pros/cons for each |
| Selected approach has rationale | Yes | References constraints from requirements |
| Key decisions are numbered | Yes | Each has rationale and impact |
| Risks have severity and mitigation | Yes | HIGH risks must have concrete mitigation |
| Acceptance criteria are verifiable | Yes | Each can be checked as pass/fail |
## Anti-Patterns
| Anti-Pattern | Why Bad | Fix |
|---|---|---|
| "The obvious approach is..." | Skips exploration, may miss better options | Always compare at least 2 |
| Spec without OUT scope | Scope creep during planning | Explicitly list what's excluded |
| Vague acceptance criteria ("works well") | Can't verify | Make criteria concrete and testable |
| No risks identified | Every design has risks | Identify at least 1 per approach |
| Copying task description as context | No analysis | Describe current state, not just goal |
## Common Issues
### Designer skips CLARIFY phase
**Cause:** Task seems clear.
**Fix:** Even "clear" tasks benefit from scope IN/OUT confirmation. At minimum, confirm scope.
### User rejects all approaches
**Cause:** Missing constraint not captured.
**Fix:** Ask: "What constraint am I missing?" — don't generate more approaches without new information.
## References
- [Spec Quality](spec-quality.md) — detailed quality criteria, approach evaluation matrix
- [Design Checklist](design-checklist.md) — phase-by-phase self-verification
章节与文件索引
按说明文件中的顺序排列。
第 1 步:在 /designer 启动时加载
步骤 2:使用相位驱动加载
规格质量标准
反模式
设计师跳过澄清阶段
文件/命令 -> spec-quality.md · design-checklist.md · pros/cons · pass/fail · IN/OUT
内容校验值 -> 4f9c48bce1ee
当前原文的自动摘译,尚未人工审校。
规格质量标准
标准 · 必需 · 检查上下文描述当前状态 · 是 · 不仅仅是“添加 X”,而是“当前 Y 存在,需要 X,因为 Z” 范围有 IN 和 OUT · 是 · OUT 项有明确的原因 至少比较 2 种方法 · 是 · 每种方法都有优点/缺点 所选方法有理由 · 是 · 引用来自需求的约束
反模式
反模式 · 为什么不好 · 修正“明显的方法是……” · 跳过探索,可能会错过更好的选择 · 总是比较至少 2 个没有超出范围的规范 · 计划期间范围蔓延 · 明确列出排除的内容 模糊的接受标准(“效果很好”) · 无法验证 · 使标准具体化并可测试 没有识别出风险 · 每个设计都有风险 · 每种方法至少识别 1 个风险
设计师跳过澄清阶段
原因:任务似乎很明确。修复:即使是“明确”的任务也会受益于范围 IN/OUT 确认。至少,确认范围。