design-ui

Designs polished, non-generic UI for TanStack Start, React, and Tailwind v4 apps.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/scomofo/midi-stage2 --skill design-ui-scomofo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-ui
Source: https://github.com/scomofo/midi-stage2/tree/main/.grok/skills/design-ui
Command: npx skills add https://github.com/scomofo/midi-stage2 --skill design-ui-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated interfaces often look generic and template-like, with ad-hoc colors, mismatched radii, emoji icons, and janky animations. This Skill enforces a design-system-first workflow so every page, dashboard, form, modal, and game overlay looks intentional and consistent. ## Core Features & Use Cases - Design tokens first: Defines palette, radii, fonts, spacing, and motion as CSS variables in Tailwind v4 @theme, banning raw hex and arbitrary values in JSX. - Quantified quality rubric: Enforces limits like 3-5 colors, 2 font families, 44px tap targets, mobile-first layouts, and contrast-safe foreground/background pairing. - Anti-slop rules and motion recipes: Blocks gradient blobs, emoji icons, and placeholder images, and provides tokenized animation patterns (modals, menus, number pop-ins, icon swaps) via shadcn/ui and Radix primitives. - Use Case: When restyling a game's start screen and HUD, apply the overlay guidance to build a readable DOM layer over the canvas with concentric radii, staggered text reveals, and reduced-motion-safe transitions. ## Quick Start Use the design-ui skill to redesign this landing page with proper design tokens, typography, and motion so it looks polished instead of generic.

Frequently Asked Questions about design-ui

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

FAQPage Schema
How do I make AI-generated UI look less generic?▼

Define a design system first: put palette, radii, and fonts as CSS variables in Tailwind v4 @theme, then compose from tokens. Ban ad-hoc hex values, emoji icons, gradient filler, and placeholder images, and limit yourself to 3-5 colors and 2 font families.

How to set up design tokens with Tailwind CSS v4?▼

Tailwind v4 is CSS-first, so declare tokens inside an @theme block in your stylesheet as CSS variables like --color-bg and --radius. Consume them as Tailwind utilities throughout components, keeping one source of truth instead of inline values.

Should I use CSS transitions or keyframe animations for interactive elements?▼

Use CSS transitions for interactive state changes like hover, toggles, and open/close because they are interruptible and retarget mid-animation. Reserve keyframe animations for one-shot sequences such as enter animations or loading states.

Does this approach work with shadcn/ui and Radix components?▼

Yes, shadcn/ui is the default component kit. Generate components into src/components/ui, style them through theme tokens rather than inline hex, and rely on Radix primitives with cva variants for accessible buttons, dialogs, dropdowns, and inputs.

Why do nested rounded corners look wrong in my UI?▼

Nested elements need concentric radii: the outer radius must equal the inner radius plus the padding between them. Using the same radius on a padded parent and child is one of the most common reasons interfaces feel off.

When should this skill not be applied to a game canvas?▼

This skill governs only DOM and overlay UI such as start screens, HUDs, menus, and pause dialogs. Gameplay canvas rendering, WebGL scenes, and game logic are out of scope and belong to a dedicated game-building skill.