define-design-principles
Turn product values and user evidence into testable design choices. Use when a team needs shared guidance for recurring tradeoffs that rules, components, or brand adjectives do not resolve.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- define-design-principles
- category
- design
- description
- Turn product values and user evidence into testable design choices. Use when a team needs shared guidance for recurring tradeoffs that rules, components, or brand adjectives do not resolve.
# define-design-principles
## Procedure
1. Define the decisions, users, product scope, constraints, and conflicts the principles must guide.
2. Gather research, support evidence, incidents, accessibility needs, strategy, and examples of good and harmful choices.
3. Identify recurring tensions such as speed versus control, density versus comprehension, or automation versus review.
4. Draft three to seven principles as verbs with an intended user outcome.
5. Add rationale, use cases, counterexamples, tradeoffs, and a question for applying each principle.
6. Rank principles or specify how conflicts are decided.
7. Test them against past decisions and two realistic new scenarios.
8. Remove slogans that always agree, cannot reject an option, or duplicate policy.
9. Approve, publish, and record ownership and review triggers.
## Guardrails
- Do not turn preferences into universal claims about users.
- Principles cannot override safety, accessibility, privacy, or evidence.
- Preserve meaningful disagreement and excluded contexts.
## Done
- A design-principles document traces each principle to evidence and a real tradeoff
- Scenario checks show that the principles change or reject options
- Conflicts, scope, ownership, and review triggers are recorded
在 GitHub 查看