ss-pattern
ss-pattern generates composed UI layouts like cards, lists, forms, and grids by combining existing design system primitives rather than creating new components. Use it when building multi-element interface sections that sit between individual components and full pages, specifying the pattern type and description to receive a reusable, token-styled component.
git clone --depth 1 https://github.com/bitjaru/styleseed /tmp/ss-pattern && cp -r /tmp/ss-pattern/engine/.claude/skills/ss-pattern ~/.claude/skills/ss-patternSKILL.md
# UI Pattern Generator ## When NOT to use - For a single primitive component → use `/ss-component` - For a full mobile screen → use `/ss-page` - For an entire multi-page user flow → use `/ss-flow` - For design tokens and color/spacing decisions → use `/ss-tokens` Pattern type: **$0** Description: $ARGUMENTS ## Available Pattern Types ### Layout Patterns - **card-section**: Card with title + content inside page section (`mx-6`) - **grid-2col**: 2-column grid of cards (`grid grid-cols-2 gap-4 px-6`) - **scroll-horizontal**: Horizontal scrolling card list (`flex gap-3 overflow-x-auto scrollbar-hide`) - **list-section**: Vertical list of items inside a card - **form-section**: Form with labeled inputs in a card - **stat-grid**: Grid of StatCard components ### Data Display Patterns - **data-table**: Table with header and rows - **detail-card**: Key-value pair display - **chart-card**: Card wrapper for a Recharts chart - **ranking-list**: Numbered ranking with highlight ### Interactive Patterns - **action-sheet**: Bottom sheet with action buttons - **filter-bar**: Horizontal filter/tab bar - **search-header**: Search input in header area ## Instructions 1. Read the design system reference: - `CLAUDE.md` for conventions - `components/ui/` for available primitives - `components/patterns/` for existing patterns 2. Compose the pattern from existing components — DO NOT recreate primitives. 3. Follow the design system layout rules: - Cards: `bg-card rounded-2xl p-6 shadow-[var(--shadow-card)]` - Section wrapper: `mx-6` for horizontal margin - Section title: `text-foreground font-bold text-[18px] mb-4` - List gap: `space-y-3` - Grid gap: `gap-4` 4. Use semantic tokens for all visual properties. 5. Make the pattern a reusable component with props for dynamic content.
Audit a component or page for accessibility issues and fix them
Audit screens for UX issues using Nielsen's heuristics and modern mobile UX best practices
Generate a new UI component following the StyleSeed design conventions
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone
Add appropriate user feedback states (loading, success, error, empty) to a component or page
Design user flows and navigation structure following proven UX patterns
Quick automated lint — detects common design system violations in seconds
Apply a named StyleSeed motion to a component — either one of the 5 personality seeds (Spring/Silk/Snap/Float/Pulse × entrance/exit/hover/press/layout) or a distinctive keyword move from the motion library (toggle-flip, toggle-curtain, reveal-blur, pop-in, shimmer, …). Translates vibe words into framer-motion code from one source of truth.