Design Rationale

What it does

This skill helps articulate the "why" behind design decisions for a product. It translates user needs, business goals, and strategic objectives into clear rationales that justify specific features or UI elements. The output provides a structured explanation of how a design choice aligns with broader product purpose and intended outcomes.

When to use it

• Justifying feature prioritization: Use this skill when needing to explain why one feature was chosen over another for inclusion in a release.
• Communicating design decisions to stakeholders: Clearly articulate the reasoning behind UI/UX choices to engineering, marketing, or leadership teams.
• Documenting product evolution: Create a record of design rationale as a product matures and requirements change.
• Onboarding new team members: Provide context for existing features by explaining their original purpose and justification.

Key capabilities

• Generates rationales linking design choices to user needs.
• Connects design decisions to business objectives.
• Provides structured explanations of product strategy alignment.

Example prompts

• "Explain the rationale behind implementing a dark mode option in our mobile app."
• "What's the reasoning for using a card-based layout on the homepage?"
• "Generate a design rationale for prioritizing user onboarding animations over detailed feature descriptions."

Tips & gotchas

The quality of the output depends heavily on providing sufficient context about the product, target users, and business goals. Without this information, the generated rationales may be generic or lack specific relevance.