design-rationale
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)
More from dragoon0x/taste-skills
visual-audit
The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.
21motion-design
Animation as communication. Feedback, orientation, emphasis, delight. If motion doesn't serve one of these four purposes, it shouldn't exist. Use when evaluating animation quality, designing transitions, or deciding whether motion adds or subtracts.
15taste-as-strategy
Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.
15teaching-taste
Help other designers develop judgment without imposing your style. Use when mentoring designers, running design education, or building team-wide quality standards.
15tradeoff-assessment
Name what was prioritized, what was sacrificed, and whether the tradeoff was right. Every design decision trades something. Use when evaluating design decisions, defending choices, or helping teams understand what they're giving up.
14field-notes
Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.
14