AGENT SKILL

ui-component

Generate a new UI component that follows StyleSeed Toss conventions for structure, tokens, accessibility, and component ergonomics.

License 许可
MIT
最近更新
2026-05-10
Stars
★ 1
Forks
1

01 前言 Front Matter

name
ui-component
risk
safe
tags
[ "ui", "components", "design-system", "frontend", "styleseed" ]
tools
[ "claude", "cursor", "codex", "gemini" ]
author
bitjaru
source
community
category
design
date_added
2026-04-08
description
Generate a new UI component that follows StyleSeed Toss conventions for structure, tokens, accessibility, and component ergonomics.
source_repo
bitjaru/styleseed
source_type
community

03 SKILL.md 正文

UI Component

Overview

Part of StyleSeed, this skill generates components that respect the Toss seed's design language instead of improvising ad hoc markup and styling. It emphasizes semantic tokens, predictable typing, reusable variants, and mobile-friendly accessibility defaults.

When to Use

  • Use when you need a new UI primitive or composed component inside a StyleSeed-based project
  • Use when you want a component to match the existing Toss seed conventions
  • Use when a component should be reusable, typed, and design-token driven
  • Use when the AI might otherwise invent spacing, colors, or interaction patterns

How It Works

Step 1: Read the Local Design Context

Before generating code, inspect the seed's source of truth:

  • CLAUDE.md for conventions
  • css/theme.css for semantic tokens
  • at least one representative component from components/ui/

If the user already has a better local example, follow the local codebase over a generic template.

Step 2: Choose the Correct Home

Place the output where it belongs:

  • src/components/ui/ for primitives and low-level building blocks
  • src/components/patterns/ for composed sections or multi-part patterns

Do not create a new primitive if an existing one can be extended safely.

Step 3: Follow the Structural Rules

Use these defaults unless the host project strongly disagrees:

  • function declaration instead of a const component
  • React.ComponentProps<> or equivalent native prop typing
  • className passthrough support
  • cn() or the project's standard class merger
  • data-slot for component identification
  • CVA or equivalent only when variants are genuinely needed

Step 4: Use Semantic Tokens Only

Do not hardcode visual values if the design system has a token for them.

Preferred examples:

  • bg-card
  • text-foreground
  • text-muted-foreground
  • border-border
  • shadow-[var(--shadow-card)]

Step 5: Preserve StyleSeed Typography and Spacing

  • Use the scale already defined by the seed
  • Prefer multiples of 6px
  • Use logical spacing utilities where supported
  • Keep display and heading text tight, body text readable, captions restrained

Step 6: Bake in Accessibility

  • Touch targets should be at least 44x44px for interactive elements
  • Keyboard focus must be visible
  • Pass through aria-* attributes where appropriate
  • Respect reduced-motion preferences for nonessential motion

Output

Provide:

  1. The generated component
  2. The target path
  3. Any required imports or dependencies
  4. Notes on variants, tokens, or follow-up integration work

Best Practices

  • Compose from existing primitives before inventing new ones
  • Keep the component API small and predictable
  • Prefer semantic layout classes over arbitrary values
  • Export named components unless the host project uses another standard consistently

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 environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

04 同仓库更多 Skills

Sansar35
Sansar35/claude-agent

zustand-store-ts

Create Zustand stores following established patterns with proper TypeScript types and middleware.

★ 1
Sansar35
Sansar35/claude-agent

zod-validation-expert

Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.

★ 1
Sansar35
Sansar35/claude-agent

zinc-database

Access ZINC (230M+ purchasable compounds). Search by ZINC ID/SMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.

★ 1
Sansar35
Sansar35/claude-agent

zarr-python

Chunked N-D arrays for cloud storage. Compressed arrays, parallel I/O, S3/GCS integration, NumPy/Dask/Xarray compatible, for large-scale scientific computing pipelines.

★ 1
Sansar35
Sansar35/claude-agent

zapier-workflows

Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.

★ 1
Sansar35
Sansar35/claude-agent

zapier-make-patterns

No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power

★ 1