ui-component

Generate UI components with StyleSeed Toss semantic tokens and accessible defaults.

25|6|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/KRISHNA0R/PORTFOLIOv2 --skill ui-component-krishna0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-component
Source: https://github.com/KRISHNA0R/PORTFOLIOv2/tree/main/.agents/skills/ui-component
Command: npx skills add https://github.com/KRISHNA0R/PORTFOLIOv2 --skill ui-component-krishna0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates ad-hoc UI markup by generating components that follow StyleSeed Toss conventions, ensuring accessibility, token-driven styling, and reusable APIs.

Core Features & Use Cases

  • Semantic tokens, typed props, and token-driven styling that align with the host design system.
  • Place outputs in the appropriate project directories (src/components/ui/ or src/components/patterns/) for predictable integration.
  • Use cases include creating primitives (buttons, inputs) or composed patterns that match Toss seed conventions.

Quick Start

Describe your component needs and run the generator to produce a ready-to-use, accessible UI component.

Frequently Asked Questions about ui-component

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate accessible UI components with semantic design tokens?

To generate accessible UI components with semantic design tokens, describe your component needs to the generator. It outputs primitives or composed patterns using StyleSeed Toss conventions, ensuring semantic tokens, typed props, and accessible defaults automatically.

How do I create frontend primitives that match my existing design system conventions?

Creating frontend primitives that match existing conventions involves generating components that adhere to StyleSeed Toss rules. This ensures token-driven styling and reusable APIs, placing generated outputs directly into predictable project directories like src/components/ui/.

Does generating UI components with this approach support custom composed patterns?

Generating UI components with this approach fully supports custom composed patterns. You can specify complex pattern requirements to the generator, which produces accessible, token-driven composed components that align with your existing StyleSeed project structure.

Where should I place generated UI components in my frontend project structure?

You should place generated UI components in specific project directories to ensure predictable integration. The generator targets src/components/ui/ for foundational primitives and src/components/patterns/ for composed components within StyleSeed-based projects.

Why use a component generator instead of writing ad-hoc frontend markup?

Using a component generator instead of ad-hoc frontend markup eliminates inconsistency by enforcing StyleSeed Toss conventions. It guarantees every generated component utilizes semantic tokens, predictable typing, and accessible defaults, maintaining strict alignment with your host design system.

Can I use this for frontend projects that do not use StyleSeed?

This generator is specifically applicable to new primitives or composed components in StyleSeed-based projects. Using it outside of a StyleSeed environment is not recommended, as the generated outputs rely heavily on existing semantic tokens and Toss seed conventions.