Agent SkillsOwl-Listener/designer-skills › design-rationale

design-rationale

GitHub

辅助撰写设计决策依据,将选择与用户需求、业务目标及原则关联。提供结构化模板,涵盖决策背景、备选方案、证据、推理、权衡及验证计划,适用于重大或争议性设计的书面辩护与记录。

designer-toolkit/skills/design-rationale/SKILL.md Owl-Listener/designer-skills

Trigger Scenarios

需要为设计决策提供书面理由 解释偏离既定模式的原因 应对对设计选择的质疑

Install

npx skills add Owl-Listener/designer-skills --skill design-rationale -g -y
More Options

Non-standard path

npx skills add https://github.com/Owl-Listener/designer-skills/tree/main/designer-toolkit/skills/design-rationale -g -y

Use without installing

npx skills use Owl-Listener/designer-skills@design-rationale

指定 Agent (Claude Code)

npx skills add Owl-Listener/designer-skills --skill design-rationale -a claude-code -g -y

安装 repo 全部 skill

npx skills add Owl-Listener/designer-skills --all -g -y

预览 repo 内 skill

npx skills add Owl-Listener/designer-skills --list

SKILL.md

Frontmatter
{
    "name": "design-rationale",
    "description": "Write rationale connecting decisions to user needs, business goals, and principles. Use when a decision needs defending in writing. For a live conversation, use `design-negotiation`."
}

Design Rationale

You are an expert in articulating the reasoning behind design decisions.

What You Do

You write clear design rationale that connects decisions to evidence, principles, and goals.

Rationale Structure

1. Decision

What design decision was made? Be specific about what was chosen.

2. Context

What problem or need prompted this decision? What constraints exist?

3. Options Considered

What alternatives were explored? Brief description of each.

4. Evidence

What informed the decision? User research, data, best practices, competitive analysis, usability testing.

5. Reasoning

Why this option over the alternatives? Connect to user needs, business goals, design principles, and technical feasibility.

6. Trade-offs

What are the known compromises? What was deprioritized and why?

7. Validation Plan

How will you know if this decision was right? What metrics or feedback will confirm?

When to Write Rationale

  • Major design direction decisions
  • Departures from established patterns
  • Controversial or debated choices
  • Decisions that will be questioned later
  • Changes from previous approaches

Rationale Quality Checklist

  • Connects to user needs (not just designer preference)
  • References evidence or principles
  • Acknowledges alternatives and trade-offs
  • Is specific enough to be useful months later
  • Written for the audience who will read it

Best Practices

  • Write rationale during the decision, not after
  • Keep it concise but complete
  • Store rationale alongside the design files
  • Reference in handoff documentation
  • Use rationale in design reviews to explain choices

Version History

  • 20e34c4 Current 2026-08-19 23:20

    优化技能描述,增加使用场景和边界说明,解决与其他技能的冲突。

  • acc3e57 2026-07-25 05:15

Same Skill Collection

design-ops/skills/design-critique/SKILL.md
design-ops/skills/design-debt-audit/SKILL.md
design-ops/skills/design-impact-reporting/SKILL.md
design-ops/skills/design-qa-checklist/SKILL.md
design-ops/skills/design-review-process/SKILL.md
design-ops/skills/design-sprint-plan/SKILL.md
design-ops/skills/handoff-spec/SKILL.md
design-ops/skills/team-workflow/SKILL.md
design-ops/skills/version-control-strategy/SKILL.md
design-research/skills/affinity-diagram/SKILL.md
design-research/skills/behavioural-analytics/SKILL.md
design-research/skills/card-sort-analysis/SKILL.md
design-research/skills/diary-study-plan/SKILL.md
design-research/skills/empathy-map/SKILL.md
design-research/skills/interview-script/SKILL.md
design-research/skills/jobs-to-be-done/SKILL.md
design-research/skills/journey-map/SKILL.md
design-research/skills/qual-quant-triangulation/SKILL.md
design-research/skills/research-repository/SKILL.md
design-research/skills/summarize-interview/SKILL.md
design-research/skills/survey-design/SKILL.md
design-research/skills/usability-test-plan/SKILL.md
design-research/skills/user-persona/SKILL.md
design-systems/skills/accessibility-audit/SKILL.md
design-systems/skills/component-spec/SKILL.md
design-systems/skills/design-system-governance/SKILL.md
design-systems/skills/design-token/SKILL.md
design-systems/skills/documentation-template/SKILL.md
design-systems/skills/icon-system/SKILL.md
design-systems/skills/localization-design/SKILL.md
design-systems/skills/motion-system/SKILL.md
design-systems/skills/naming-convention/SKILL.md
design-systems/skills/pattern-library/SKILL.md
design-systems/skills/theming-system/SKILL.md
designer-toolkit/skills/case-study/SKILL.md
designer-toolkit/skills/design-negotiation/SKILL.md
designer-toolkit/skills/design-system-adoption/SKILL.md
designer-toolkit/skills/design-token-audit/SKILL.md
designer-toolkit/skills/presentation-deck/SKILL.md
designer-toolkit/skills/ux-writing/SKILL.md
interaction-design/skills/animation-principles/SKILL.md
interaction-design/skills/conversational-ux/SKILL.md
interaction-design/skills/doherty-threshold/SKILL.md
interaction-design/skills/error-handling-ux/SKILL.md
interaction-design/skills/feedback-patterns/SKILL.md
interaction-design/skills/fitts-law/SKILL.md
interaction-design/skills/form-design/SKILL.md
interaction-design/skills/gesture-patterns/SKILL.md
interaction-design/skills/hicks-law/SKILL.md

Metadata

Files
0
Version
9a6930c
Hash
d451c85c
Indexed
2026-07-25 05:15

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-09-10 06:35
浙ICP备14020137号-1 $방문자$