Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Skill · Web Development

Ui component

Generate a new UI component following the StyleSeed design conventions

Agentic Awesome SkillsLicense: MITAdded Sep 5, 2026
Use it in my AI

How to use it

  1. Start your plan and connect your AI once
  2. Add the skill to your AI, one time only: press Copy skill and paste it into your AI's instructions: a project in ChatGPT, Claude or Grok, a Gem in Gemini, an agent in Microsoft 365 Copilot, or a rule in Cursor. It stays there for every new chat. In Kimi, paste it at the start of a new chat.
  3. Ask for the task in your own words, or say it directly:
Use the Ui component skill to help me with this.
SKILL.md

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
  1. 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
  1. 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)]
  1. 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)
  1. 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
  1. Export the component as a named export (not default)
  1. Place the file in the appropriate directory:
  • Primitive/reusable → src/components/ui/
  • Composed pattern → src/components/patterns/

Example

User request:

Generate a new UI component following the StyleSeed design conventions.

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.