ui

Analyze UI component architecture and generate tokenized component library structures.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill ui-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/ui
Command: npx skills add https://github.com/arbazkhan971/godmode --skill ui-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes consistent, maintainable UI component architecture to reduce design drift, remove hardcoded styles, and ensure components are testable, accessible, and reusable across projects.

Core Features & Use Cases

  • Architecture Audit: Detects framework and styling approach, counts components, and surfaces design token and spacing violations.
  • Design Token & CSS Guidance: Recommends when to use Tailwind, CSS Modules, or CSS-in-JS and enforces tokenization to eliminate hardcoded colors and spacing.
  • Component Library & Storybook Setup: Provides folder structure templates, naming and API conventions, Storybook initialization steps, and rules for tests and accessibility.
  • Use Case: Migrate a legacy SCSS codebase to a tokenized component library with Storybook coverage and automated visual/accessibility checks.

Quick Start

Use the ui skill to audit your repository's component library, report token violations, and produce a Storybook setup and component structure plan.

Frequently Asked Questions about ui

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

FAQPage Schema
How do I set up a component library with Storybook and design tokens?

To set up a component library with Storybook and design tokens, audit your existing framework and styling approach to detect hardcoded values, then generate folder structure templates and Storybook configuration rules that enforce tokenization and accessibility standards.

What is the best way to migrate legacy SCSS to a tokenized component library?

Migrating legacy SCSS to a tokenized component library involves auditing the codebase to surface spacing and color violations, replacing hardcoded styles with design tokens, and establishing component folder templates with automated visual and accessibility checks.

Does this UI component architecture approach work with Svelte and Angular?

Yes, this UI component architecture approach works with Svelte and Angular, along with React and Vue. It detects your specific framework and styling approach to provide tailored component hierarchy definitions, CSS architecture decisions, and naming conventions.

How do I eliminate hardcoded colors and spacing in my CSS architecture?

To eliminate hardcoded colors and spacing in your CSS architecture, audit your components for design token violations and enforce tokenization by recommending appropriate styling approaches like Tailwind, CSS Modules, or CSS-in-JS.

When do I need a design system audit for my front-end project?

You need a design system audit for your front-end project when you want to reduce design drift, ensure components are testable and accessible, and establish a consistent, maintainable UI component architecture by counting components and surfacing spacing violations.