design-rationale
The design-rationale skill guides designers in documenting the reasoning behind design decisions through a structured seven-part framework: decision, context, options considered, evidence, reasoning, trade-offs, and validation plan. Use this skill when making major design choices, departing from established patterns, addressing controversial decisions, or anticipating future questions about design direction to create decision documentation that connects to user needs and business goals.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/design-rationale && cp -r /tmp/design-rationale/designer-toolkit/skills/design-rationale ~/.claude/skills/design-rationaleSKILL.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 - Store rationale alongside the design files - Reference in handoff documentation - Use rationale in design reviews to explain choices
Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.
Communicate design's contribution to business and user outcomes in terms that resonate with stakeholders.
Create QA checklists for verifying design implementation accuracy.
Establish design review gates with criteria, checklists, and approval workflows.
Plan and facilitate design sprints from challenge framing through prototype testing.
Create developer handoff specifications with measurements, behaviors, assets, and edge cases.
Design team workflows covering task management, collaboration rituals, and tooling.