design-principles

Define concise design principles with titles, rationale, and examples.

2.0k|325|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill design-principles-owl-listener
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-principles
Source: https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/design-principles
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill design-principles-owl-listener

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to reach quick, consistent design decisions in the face of trade-offs. This skill defines a concise, actionable set of guiding principles that align product, design, and engineering voices.

Core Features & Use Cases

  • Clearly articulated principles (3-6 words per title) with statements, rationales, and practical examples.
  • Supports decision-making during design reviews, feature scoping, and interface audits.
  • Trade-off resolution templates that help teams rank and apply principles under conflicting goals.

Quick Start

Draft a prioritized set of design principles and apply them in upcoming design reviews to resolve trade-offs.

Frequently Asked Questions about design-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I establish design principles to align product, design, and engineering teams?

Establish design principles by drafting concise, actionable titles with rationales and practical examples to align product, design, and engineering teams. This ensures consistent decision-making across product work from research alignment to UI decisions.

What is the best way to resolve design trade-offs during feature scoping and interface audits?

The best way to resolve design trade-offs is using trade-off resolution templates that help teams rank and apply principles under conflicting goals. This guides decisions during design reviews, feature scoping, and interface audits.

Can I use these design principles to prioritize consistency and accessibility in UI decisions?

Yes, you can use design principles to prioritize consistency and accessibility in UI decisions. They provide actionable guidance for product teams facing trade-offs, ensuring accessibility and consistency are evaluated against past decisions.

How do I write design principles that are testable against past product decisions?

Write testable design principles by defining clear titles of 3-6 words, accompanied by statements, rationales, and practical examples. This structure ensures principles are actionable and verifiable against past product team decisions.

Does this approach to design principles require specific frameworks or dependencies?

No, this approach to design principles requires no specific frameworks or dependencies. It is a standalone methodology for decision-making that any product, design, or engineering team can adopt to achieve team-alignment.