UI Component Generator

VerifiedSafe

Generate a new UI component following StyleSeed design conventions, with token support and accessibility.

Sby Skills Guide Bot
DevelopmentIntermediate
7/30/2026
Claude Code
#react#tailwind#design-system#ui-components#typescript

Recommended for

Automated summary

Generates a new React UI component that follows StyleSeed design conventions, after reading the project's design seed files for context.

Strengths

  • Enforces consistent conventions: `function` declarations, a `data-slot` attribute, `React.ComponentProps<>` typing, and a `className` prop for overrides.
  • Pulls from design tokens in `css/theme.css` (semantic colors, shadows, radii, motion durations) instead of inline hex values.
  • Includes an accessibility checklist covering 44px touch targets, `focus-visible` rings, and `prefers-reduced-motion`.
  • Directs the file to `src/components/ui/` or `src/components/patterns/` depending on whether it is a primitive or a composed pattern.

Limitations

  • Only applies to StyleSeed projects that have a `components/ui/` directory and Tailwind v4.
  • Relies on the reference files (`CLAUDE.md`, `css/theme.css`, `button.tsx`) being present to work as intended.
  • No automated verification step (lint, tests) is described, so the generated code still needs human review.
When to use it

Use it when adding a single new component to an existing StyleSeed project that must match its design conventions.

When not to use it

Avoid it for full pages, composed multi-component patterns, or non-StyleSeed projects (including pre-v4 Tailwind setups).

Security analysis

Safe
Quality score88/100

The skill only instructs reading project files and generating React/TypeScript UI component code following design conventions. It does not execute commands, access network, handle credentials, or perform destructive actions. No risky tools are declared or used.

No concerns found

How this analysis is made

Examples

Status badge with variants
Create a Badge component in src/components/ui with CVA variants for success, warning, and destructive states, using StyleSeed semantic color tokens.
Accessible tooltip pattern
Generate a Tooltip component following StyleSeed conventions and place it in src/components/patterns/tooltip.tsx — it must meet the 44px touch target and focus-visible requirements.
Clickable card primitive
Add a Card component to src/components/ui that accepts a className override, uses shadow-[var(--shadow-card)] and rounded-lg, and supports aria-* passthrough.

name: ui-component description: Generate a new UI component following the StyleSeed design conventions risk: unknown source: https://github.com/bitjaru/styleseed/tree/main/engine/.claude/skills/ss-component source_repo: bitjaru/styleseed source_type: community date_added: 2026-07-01 license: MIT license_source: https://github.com/bitjaru/styleseed/blob/main/LICENSE

UI Component Generator

When to Use

Use this skill when you need generate a new UI component following the StyleSeed design conventions.

When NOT to use

  • For full-page scaffolding → use /ss-page
  • For composed multi-component patterns → use /ss-pattern
  • For tweaking an existing component — just edit the file directly
  • For non-StyleSeed projects (no components/ui/ directory or no Tailwind v4)

Generate a new component: $0 Description: $ARGUMENTS

Instructions

  1. First, read the design system seed for context:

    • Read CLAUDE.md for component conventions
    • Read css/theme.css for available design tokens
    • Read components/ui/button.tsx as a reference pattern
  2. Follow these conventions strictly:

    • Use function declaration (not const)
    • Add data-slot="component-name" attribute
    • Use cn() from @/components/ui/utils for all className merging
    • Use React.ComponentProps<> for prop typing
    • Always support className prop for overrides
    • Use CVA (class-variance-authority) if the component has variants
    • Use semantic color tokens (bg-card, text-foreground) — never inline hex
  3. Design token usage:

    • Colors: text-foreground, bg-card, text-brand, text-muted-foreground, border-border
    • Shadows: shadow-[var(--shadow-card)], shadow-[var(--shadow-elevated)]
    • Radius: rounded-md, rounded-lg, rounded-2xl
    • Spacing: multiples of 6px (p-1.5, p-3, p-6)
    • Motion: duration-[var(--duration-fast)], ease-[var(--ease-default)]
  4. Typography rules:

    • Display (36-48px): leading-none tracking-[-0.02em]
    • Heading (18-24px): leading-snug tracking-[-0.01em]
    • Body (14-17px): leading-normal (default tracking)
    • Caption uppercase (10-13px): tracking-[0.05em]
    • Use size-* shorthand instead of w-* h-*
    • Use ms-*/me-* instead of ml-*/mr-* (logical properties)
  5. Accessibility requirements:

    • Minimum touch target: 44x44px (min-h-11 min-w-11)
    • Support aria-* attributes passthrough
    • Use focus-visible:ring-2 focus-visible:ring-ring for keyboard focus
    • Respect prefers-reduced-motion for animations
  6. Export the component as a named export (not default)

  7. Place the file in the appropriate directory:

    • Primitive/reusable → src/components/ui/
    • Composed pattern → src/components/patterns/

Limitations

  • Use this skill only when the task clearly matches its upstream source and local project context.
  • Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
  • Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/ui-component-generator-ms71b3p5/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/ui-component-generator-ms71b3p5' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ui-component-generator-ms71b3p5/download' --output '.skill-downloads/ui-component-generator-ms71b3p5/SKILL.md.part' && mv '.skill-downloads/ui-component-generator-ms71b3p5/SKILL.md.part' '.skill-downloads/ui-component-generator-ms71b3p5/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/ui-component-generator-ms71b3p5/SKILL.md' && test -s '.skill-downloads/ui-component-generator-ms71b3p5/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ui-component' && cp -R '.skill-downloads/ui-component-generator-ms71b3p5' '.claude/skills/ui-component'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/ui-component-generator-ms71b3p5'

openskills read 'ui-component-generator-ms71b3p5'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/ui-component-generator-ms71b3p5/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills