This is the skill you want when "our UI feels inconsistent" but you're not sure if you need new components, tokens, or just better rules. It forces you to classify the problem first (foundations, cross-surface alignment, primitive governance, or handoff) before generating examples or writing code. The core discipline is routing work out early: keep system-level token and naming decisions here, but send component API design to ui-component-patterns, layout fixes to responsive-design, and accessibility remediation to web-accessibility. It's opinionated about rules before examples and includes reference docs on token governance, scope boundaries, and system modes. Best for teams that keep redesigning the same surface because they never decided what stays consistent across products.
npx -y skills add akillness/oh-my-skills --skill design-system --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
leonxlnx/taste-skill
supercent-io/skills-template
supercent-io/skills-template