UI Pattern
Overview
Part of StyleSeed, this skill builds reusable composed patterns from the seed's primitives. It is intended for sections like card lists, grids, form blocks, ranking lists, and chart wrappers that appear across multiple pages and need to look deliberate rather than ad hoc.
When to Use
- Use when you need a reusable layout pattern rather than a one-off page section
- Use when a page repeats the same arrangement of cards, rows, filters, or data blocks
- Use when you want to build from existing StyleSeed primitives instead of copying markup
- Use when you want a pattern component with props for dynamic content
How It Works
Step 1: Identify the Pattern Type
Common pattern families include:
- card section
- two-column grid
- horizontal scroller
- list section
- form section
- stat grid
- data table
- detail card
- chart card
- filter bar
- action sheet
Step 2: Read the Available Building Blocks
Inspect both:
components/ui/ for primitives
components/patterns/ for neighboring patterns that can be extended
The goal is composition, not duplication.
Step 3: Apply StyleSeed Layout Rules
Keep the Toss seed defaults intact:
- card surfaces on semantic tokens
- rounded corners from the system scale
- shadow tokens instead of improvised shadow values
- consistent internal padding
- section wrappers that align with the page margin system
Step 4: Make the Pattern Dynamic
Expose data through props instead of hardcoding content. If a pattern has multiple variants, keep the API explicit and small.
Step 5: Keep the Pattern Reusable Across Pages
Avoid page-specific assumptions unless the user explicitly wants a one-off section. If the markup only works on one route, it probably belongs in a page component, not a shared pattern.
Output
Provide:
- The generated pattern component
- The target location
- Expected props and usage example
- Notes on which existing primitives were reused
Best Practices
- Start from the smallest existing building block that solves the problem
- Keep container, section, and item responsibilities separate
- Use tokens and spacing rules consistently
- Prefer extending a pattern over adding a near-duplicate sibling
Additional Resources
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for enprojectnment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: ui-pattern3description: "Generate reusable UI patterns such as card sections, grids, lists, forms, and chart wrappers using StyleSeed Toss primitives."4category: design5risk: safe6source: community7source_repo: bitjaru/styleseed8source_type: community9date_added: "2026-04-08"10author: bitjaru11tags: [ui, patterns, design-system, reuse, styleseed]12tools: [claude, cursor, codex, gemini]13metadata:14 source: https://skillmd.com/skills/phoroth/ui-pattern15---1617# UI Pattern1819## Overview2021Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill builds reusable composed patterns from the seed's primitives. It is intended for sections like card lists, grids, form blocks, ranking lists, and chart wrappers that appear across multiple pages and need to look deliberate rather than ad hoc.2223## When to Use24- Use when you need a reusable layout pattern rather than a one-off page section25- Use when a page repeats the same arrangement of cards, rows, filters, or data blocks26- Use when you want to build from existing StyleSeed primitives instead of copying markup27- Use when you want a pattern component with props for dynamic content2829## How It Works3031### Step 1: Identify the Pattern Type3233Common pattern families include:34- card section35- two-column grid36- horizontal scroller37- list section38- form section39- stat grid40- data table41- detail card42- chart card43- filter bar44- action sheet4546### Step 2: Read the Available Building Blocks4748Inspect both:49- `components/ui/` for primitives50- `components/patterns/` for neighboring patterns that can be extended5152The goal is composition, not duplication.5354### Step 3: Apply StyleSeed Layout Rules5556Keep the Toss seed defaults intact:57- card surfaces on semantic tokens58- rounded corners from the system scale59- shadow tokens instead of improvised shadow values60- consistent internal padding61- section wrappers that align with the page margin system6263### Step 4: Make the Pattern Dynamic6465Expose data through props instead of hardcoding content. If a pattern has multiple variants, keep the API explicit and small.6667### Step 5: Keep the Pattern Reusable Across Pages6869Avoid page-specific assumptions unless the user explicitly wants a one-off section. If the markup only works on one route, it probably belongs in a page component, not a shared pattern.7071## Output7273Provide:741. The generated pattern component752. The target location763. Expected props and usage example774. Notes on which existing primitives were reused7879## Best Practices8081- Start from the smallest existing building block that solves the problem82- Keep container, section, and item responsibilities separate83- Use tokens and spacing rules consistently84- Prefer extending a pattern over adding a near-duplicate sibling8586## Additional Resources8788- [StyleSeed repository](https://github.com/bitjaru/styleseed)89- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ui-pattern/SKILL.md)9091## Limitations92- Use this skill only when the task clearly matches the scope described above.93- Do not treat the output as a substitute for enprojectnment-specific validation, testing, or expert review.94- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.