ui-implementor

Generate Tailwind config, theming, and shadcn components from design tokens.

8|3|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ydnikolaev/antigravity-factory --skill ui-implementor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-implementor
Source: https://github.com/ydnikolaev/antigravity-factory/tree/main/src/skills/ui-implementor
Command: npx skills add https://github.com/ydnikolaev/antigravity-factory --skill ui-implementor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates design tokens and system specifications into a production-ready frontend component library, accelerating consistent UI implementation.

Core Features & Use Cases

  • Token-driven conversion: generates a Tailwind configuration and CSS theming from design tokens.
  • Component generation: builds shadcn-based Vue or React components aligned to tokens and design specs.
  • Theming & accessibility: implements light/dark theming and accessible component states across breakpoints.

Quick Start

Provide design tokens from the design team (e.g., project/docs/active/design) and run the token-to-code workflow to generate Tailwind config, theming, and initial shadcn components.

Frequently Asked Questions about ui-implementor

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

FAQPage Schema
How do I convert design tokens into a Tailwind configuration?

You convert design tokens into a Tailwind configuration by providing your token specifications to the workflow, which then automatically generates a production-ready Tailwind config and CSS theming.

Can I generate shadcn components from design tokens for a React or Vue app?

Yes, you can generate shadcn components from design tokens for React or Vue apps. The skill builds token-aligned shadcn components to accelerate consistent UI implementation.

Does this design-to-code workflow support light and dark theming?

Yes, this design-to-code workflow supports light and dark theming. It translates your design tokens into accessible component states and responsive theming across different breakpoints.

What is the best way to implement accessible component states using a token-driven system?

The best way to implement accessible component states is by using a token-driven system that automatically enforces accessibility requirements and responsive behavior when generating your frontend component library.

Do I need to provide specific design token files to start the component generation process?

Yes, you need to provide design token files from your design team, such as those located in a project docs directory, to start the token-to-code workflow and generate the initial components.

How does token-driven styling enforce consistency in a frontend component library?

Token-driven styling enforces consistency by directly translating system specifications into a frontend component library, ensuring all generated Tailwind configurations and shadcn components match the original design tokens.