Design rationale
Skill Dragoon0x/taste-skills/skills/articulation/design-rationale
Agent skills for design taste and visual judgment. Hierarchy, typography, color, spacing, interaction quality, and the invisible decisions that separate good design from great design
npx -y skills add Dragoon0x/taste-skills --skill design-rationaleAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Defend a design decision to skeptical stakeholders with structure and evidence. Use when presenting design work, writing design documentation, or pushing back on requests to change something.
SKILL.md
1.3 KB, as published. Nobody here has run it
Design Rationale
Convince the room with structure, not feelings.
How to use
/design-rationaleApply rationale constraints to defend design decisions in this conversation.
Constraints
Rationale Structure
- MUST include all four elements in one paragraph:
- What you chose
- What you didn't choose (and why)
- What principle guided the decision
- What outcome you expect
- MUST connect to user behavior or business goals, not aesthetic preference
- NEVER defend a design decision with "it feels right" or "it looks better"
Anticipate Objections
- MUST address the most likely pushback before it's raised
- SHOULD acknowledge what's lost by this choice (the tradeoff)
- MUST have a fallback position if the primary argument doesn't land
Anti-Patterns
- Defending decisions by appealing to authority ("Apple does it this way")
- Using data as a shield without explaining the logic ("our A/B test showed...")
- Getting defensive when challenged instead of engaging with the objection
- Over-explaining simple decisions (not every choice needs a thesis)