web-component-design

Master React, Vue, and Svelte component patterns including CSS-in-JS, composition strategies, and reusable component architecture. Use when building UI component libraries, designing component APIs, or implementing frontend design systems.

By wshobson · 11,884 installs

npx skills add wshobson/agents --skill web-component-design

Source repository · Upstream listing

Web Component Design Build reusable, maintainable UI components using modern frameworks with clean composition patterns and styling approaches. When to Use This Skill Designing reusable component libraries or design systems Implementing complex component composition patterns Choosing and applying CSS in JS solutions Building accessible, responsive UI components Creating consistent component APIs across a codebase Refactoring legacy components into modern patterns Implementing compound components or render props Core Concepts 1. Component Composition Patterns Compound Components : Related components that work together Render Props : Delegate rendering to parent Slots (Vue/Svelte) : Named content injection points 2. CSS in JS Approaches Solution Approach Best For Tailwind CSS Utility classes Rapid prototyping, design systems CSS Modules Scoped CSS files Existing CSS, gradual adoption styled components Template literals React, dynamic styling Emotion Object/template styles Flexible, SSR friendly Vanilla Extract Zero runtime Performance critical apps 3. Component API Design Principles : Use semantic prop names ( isLoading vs loading ) Provide sensible defaults Support composition via children Allow style overrides via className or style Quick Start: React Component with Tailwind Framework Patterns React: Compound Components Vue 3: Composables Svelte 5: Runes Best Practices 1. Single Responsibility : Each component does one thing well 2. Prop Drilling Prevention : Use context for deeply nested data 3. Accessible by Default : Include ARIA attributes, keyboard support 4. Controlled vs Uncontrolled : Support both patterns when appropriate 5. Forward Refs : Allow parent access to DOM nodes 6. Memoization : Use React.memo , useMemo for expensive renders 7. Error Boundaries : Wrap components that may fail Common Issues Prop Explosion : Too many props consider composition instead Style Conflicts : Use scoped styles or CSS Modules Re render Cascades : Profile with React DevTools, memo appropriately Accessibility Gaps : Test with screen readers and keyboard navigation Bundle Size : Tree shake unused component variants