ui-components

Create reusable UI components with design tokens, Tailwind, and shadcn/ui primitives.

1.5k|875|Updated Aug 20, 2021
One-click install
npx skills add https://github.com/saleor/storefront --skill ui-components-saleor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-components
Source: https://github.com/saleor/storefront/tree/main/.claude/skills/ui-components
Command: npx skills add https://github.com/saleor/storefront --skill ui-components-saleor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI development often suffers from inconsistent styling and duplicated patterns. This skill provides best practices for creating reusable UI components using design tokens, Tailwind, and shadcn/ui primitives.

Core Features & Use Cases

  • Create reusable components and primitives with a consistent design system.
  • Style components using Tailwind and design tokens to ensure a cohesive UI.
  • Decide between Server and Client Components to optimize performance.

Quick Start

Create a new UI component under src/ui/components, apply design tokens, and export it for reuse.

Frequently Asked Questions about ui-components

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create reusable React components with design tokens and Tailwind?

To create reusable React components with design tokens, build UI primitives using shadcn/ui, apply design-token-based styling, and integrate Tailwind for a cohesive UI. Export these standardized components for reuse across feature pages.

When do I need Server Components versus Client Components in React?

Server versus Client Component decisions are needed when optimizing rendering performance in React. Use this approach to guide rendering choices across shared components and feature pages like PDP and PLP for better load management.

Does this approach work with shadcn-ui and Tailwind for styling?

Yes, this approach works directly with shadcn-ui and Tailwind. It enforces design-token-based styling alongside shadcn/ui primitives to standardize UI styling and eliminate duplicated patterns across your application.

What's the best way to standardize UI styling across shared components?

The best way to standardize UI styling is to apply reusable design tokens to shadcn/ui primitives. This ensures a consistent design system across shared components and feature pages while preventing duplicated styling patterns.

Why does inconsistent styling happen in UI development and how to fix it?

Inconsistent styling happens due to duplicated patterns across shared components. Fix it by enforcing design-token-based styling with Tailwind and shadcn/ui primitives, establishing a clear export pattern for reuse.