ui-design-ethos
Design System Skill
This skill produces principled, production-ready design decisions grounded in three reference volumes. It operates in two modes. Detect the correct mode from context — don't ask unless genuinely ambiguous.
Modes
Mode 1: /ui-spec — UI Specification
Trigger: User describes a screen, feature, or component they need to build and wants a design spec before coding.
What it does: Outputs a structured spec covering layout decisions, component choices, spacing values, interaction states, dark/light variants, accessibility requirements, and implementation notes.
Read before running: references/vol3-saas-patterns.md (relevant component sections) + references/vol2-visual-interaction.md (layout patterns section)
Mode 2: /ui-audit — Design Audit
Trigger: User shares existing UI (component code, screenshot description, Figma spec, or live URL) and wants a review.
More from zackbart/skills
optimize-prompt
>
9kysely
>
7second-opinion
>
5update-docs
>
5design-system-patterns
>
5ethos
Conduct a structured interview and write a project's ethos.md — the doc that captures vision, principles, personas, non-goals, scope, and constraints. Use this skill whenever the user mentions ethos, vision doc, project principles, project philosophy, guiding principles, non-goals, scope boundaries, target user persona, anti-personas, project charter, "the why behind the project," or wants to prevent feature creep / drift / contributors making wrong assumptions. Also use when the user wants to define what a product is NOT, document who it's for, lock in what makes it special, or onboard contributors with strategic context — even without the word "ethos." Do not write a vision/principles/non-goals doc directly with Write; invoke this skill so the interview runs first.
4