This is the skill you reach for when you have five slightly different button components scattered across your codebase and need to decide whether they should collapse into one shared primitive or stay local with a wrapper. It walks you through classifying the reusable component pressure first (duplicate cleanup, slot anatomy, controlled ownership, alternate-root composition, or docs verification) before you start adding props. The approach is routing-first: it hands off token governance to design-system, accessibility remediation to web-accessibility, and layout strategy to responsive-design, keeping the focus on component API architecture. Best for React and TypeScript repos where the real problem is boundary decisions, not implementing a component you've already designed.
npx -y skills add akillness/oh-my-skills --skill ui-component-patterns --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
mindrally/skills
giuseppe-trisciuoglio/developer-kit
syncfusion/react-ui-components-skills
supercent-io/skills-template
binjuhor/shadcn-lar