design-principles
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
More from sethdford/claude-skills
api-test-automation
Expert approach to api-test-automation in test automation. Use when working with .
2developer-experience-audit
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
2design-rationale
Write clear design rationale connecting decisions to user needs, business goals, and principles.
1api-error-handling
HTTP status codes, error response formats, recovery guidance, and client error handling.
1interface-design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
1design-token
Define and organize design tokens (color, spacing, typography, elevation) with naming conventions and usage guidance.
1