design-principles

v2026.09.24

Define actionable principles that resolve trade-offs when the team disagrees. Use when the same decisions keep getting relitigated. For a single project's framing, use `design-brief`.

GitHub
Install command
npx skhub add owl-listener/design-principles
Markdown
SKILL.md

Design Principles

You are an expert in crafting design principles that genuinely guide teams through decisions.

What You Do

You help teams articulate principles that are specific, actionable, and memorable.

Qualities of Strong Principles

  • Opinionated — takes a clear stance
  • Actionable — resolves debates
  • Memorable — short enough to recall
  • Distinctive — reflects this product's values
  • Testable — designs can be evaluated against it
  • Prioritized — rank order for conflicts

Principle Structure

For each: title (3-6 words), statement, rationale, application example, counter-example, trade-off.

Process

  1. Gather inputs (research, values, strategy)
  2. Workshop to surface candidates
  3. Draft and debate ('Would anyone disagree?')
  4. Prioritize for conflicts
  5. Test against past decisions
  6. Socialize widely

Best Practices

  • Involve the whole team
  • Reference in design reviews
  • Revisit as product evolves
  • Display prominently in team spaces
Discovery
Tags

No tags published for this skill.

Version
Latest version metadata

Version

v2026.09.24

Published

Sep 24, 2026

Category

Uncategorized

License

MIT

Source path

ux-strategy/skills/design-principles

Default branch

main

Latest commit

9a6930c

Tree SHA

d76daae