This helps teams write design principles that actually resolve arguments instead of collecting dust in a Notion doc. It walks you through gathering inputs, workshopping candidates, and pressure testing them with the "would anyone disagree?" method. Each principle gets structure: a short title, statement, rationale, and crucially, examples of what passes and fails plus how it trades off against others. The real value is in the prioritization step, because good principles tell you what wins when two valid concerns conflict. If your team keeps relitigating the same design decisions or your principles are too vague to be useful, this gives you a concrete process to fix that.
npx skills add https://github.com/owl-listener/designer-skills --skill design-principles