Design Rationale

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`.

3,414 stars 447 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill design-rationale
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/designer-toolkit/skills/design-rationale ~/.claude/skills/design-rationale

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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
Read the full skill on GitHub

Details

Skill name
design-rationale
Path
designer-toolkit/skills/design-rationale/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the Design Rationale skill do?

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`.

How do I install the Design Rationale skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Design Rationale popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Documentation Template

3.4k

Owl-Listener/designer-skills

Generate a reusable documentation scaffold for components, patterns, or guidelines. Use when standardising how the system is documented. For the content of one component's spec, use `component-spec`.

Writing & Content447

Design Brief

3.4k

Owl-Listener/designer-skills

Write a project brief — problem space, constraints, audience, and success criteria. Use at kickoff for one specific project. For long-horizon aspiration use `north-star-vision`; for reusable decision rules use `design-principles`.

Writing & Content447

Interview Script

3.4k

Owl-Listener/designer-skills

Write a structured interview guide — warm-up, core exploration, and wrap-up. Use before running interviews. For analysing what comes back, use `summarize-interview`.

Writing & Content447

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.