ui

Orchestrates UI design direction, system tokens, screen building, audits, and verification for frontend work.

1|Updated Aug 17, 2026
One-click install
npx skills add https://github.com/NalinDalal/skillset --skill ui-nalindalal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui
Source: https://github.com/NalinDalal/skillset/tree/main/skills/ui/ui-core
Command: npx skills add https://github.com/NalinDalal/skillset --skill ui-nalindalal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend work often ships as generic, templated-looking interfaces with missing states, weak hierarchy, and inconsistent interactions. This Skill provides a five-phase process that takes a UI from direction picking through design system definition, screen building, redesign or audit, and a mandatory verification gate before anything ships. ## Core Features & Use Cases - Five-phase workflow: pick the visual direction, design the token system, build the screen, redesign or audit existing UI, and verify against a finish gate covering seven viewports, accessibility, dark mode, and copy. - Product-ready quality bar: enforces complete UI states (empty, loading, error, disabled), realistic content, responsive reflow, keyboard accessibility, and intentional motion instead of decorative animation. - Reference library: nine reference files covering accessibility, build discipline, copywriting, dark mode, direction picking, redesign audits, responsive design, style recipes, and design system tokens. - Use Case: Ask the agent to build a dashboard for a new SaaS product. The Skill infers the design direction, outputs Tailwind tokens, builds the screen with real content and all states, then runs the verification gate across viewports and themes before declaring it done. ## Quick Start Ask the agent to design and build a new page or redesign an existing screen, and it will run the matching phase and verify the result before shipping.

Frequently Asked Questions about ui

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

FAQPage Schema
How do I make an AI-generated UI not look templated?▼

Run the direction phase to establish product identity: a signature color, a typeface matching the brand voice, and one memorable interaction. Then apply the anti-slop rules that ban purple gradients, glowing buttons, three equal cards, and default fonts like Inter and Roboto.

How to redesign an existing UI without rewriting from scratch?▼

Use the scan, diagnose, fix workflow: read the codebase, write a feel contract, audit by category (typography, color, layout, interactivity, content), then fix in priority order P0 through P3. Preserve information architecture, slugs, nav labels, copy voice, and analytics.

What design tokens should a Tailwind design system define?▼

Define one accent under 80% saturation, one gray family, one radius scale, semantic color roles (canvas, surface, text, muted, border), a modular type scale, and spacing tokens. Output them as Tailwind v4 @theme or v3 theme.extend, never raw hex in JSX.

Does this approach support dark mode and accessibility requirements?▼

Yes. Dark mode uses CSS variable architecture with redesigned tokens rather than inversion, and both themes must hit AA contrast (4.5:1 body text, 3:1 large text and components). Focus management, ARIA patterns, and keyboard paths are built in during the build phase.

What checks happen before a UI is considered finished?▼

The verify gate requires rendering at seven viewports without overflow, empty/loading/error states on every surface, keyboard navigation without traps, reduced-motion support, AA contrast in both themes, a clean 10-minute user journey, and passing lint and build, all backed by captured evidence.