Design Principles

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

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`.

Instructions onlyDesign & Creative

AI-generated overview

Helps teams write actionable design principles that resolve recurring product decisions and trade-offs.

What it does: This skill guides a team through articulating design principles that are specific, actionable, memorable, distinctive, testable and prioritized. It defines a per-principle structure (title, statement, rationale, application example, counter-example, trade-off) and a six-step process from gathering inputs to socializing the result. It also lists best practices for keeping principles in use during design reviews.
When to use it: Use it when the same design decisions keep being relitigated and the team needs shared principles to settle trade-offs. It fits workshops where research, values and strategy are turned into ranked principles. For framing a single project instead, the skill points to a separate design-brief skill.
Requirements: No scripts or special tooling; it is an instructions-only skill that needs a team workshop and access to research, values and strategy inputs.

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

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

Best Practices

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

Source and attribution

Source:owl-listener/designer-skillsinux-strategy/skills/design-principlesat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Design Principles

Design Principles

What You Do

Qualities of Strong Principles

Principle Structure

Process

Best Practices

Source and attribution

More from owl-listener/designer-skills

Zeigarnik Effect

Teslers Law

Von Restorff Effect

State Machine

Visual Hierarchy

Serial Position Effect

More in Design & Creative

Theme Factory

Slack Gif Creator

Frontend Design

Canvas Design

Brand Guidelines

Frontend Design