ui-ux-design-engine
Skill1 starsChanged 4 months agoMITView on GitHub
Vercel & Design Systems Inspired UI/UX Engineering Playbook. Enforces semantic HSL design tokens, responsive typography hierarchy, fluid micro-interactions, glassmorphism, dark/light contrast correctness, accessible interaction states, component composition, and strict visual finish gates.
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- frontend/AGENTS.mdAGENTS.md
- autoresearchSkill
- brainstormingSkill
- brandkitSkill
- create-github-action-workflow-specificationSkill
- design-taste-frontendSkill
- design-taste-frontend-v1Skill
- dispatching-parallel-agentsSkill
- dokion-hardeningSkill
- dokion-playbook-creatorSkill
- dokion-playbook-hubSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- full-output-enforcementSkill
- git-commitSkill
- github-publishing-workflowSkill
- google-ai-studio-web-editorSkill
- gpt-tasteSkill
- high-end-visual-designSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- industrial-brutalist-uiSkill
- minimalist-uiSkill
- receiving-code-reviewSkill
- redesign-existing-projectsSkill
- requesting-code-reviewSkill
- stitch-design-tasteSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
- autoresearchSkill
- dokion-playbook-creatorSkill
- dokion-playbook-hubSkill
- dokion-hardeningSkill
- agent-playbookSkill
- archifySkill
- autoresearchSkill
- brainstormingSkill
- dispatching-parallel-agentsSkill
- dokion-automationSkill
- dokion-fullstackSkill
- dokion-hardeningSkill
- dokion-playbook-creatorSkill
- dokion-playbook-hubSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- github-publishing-workflowSkill
- google-ai-studio-web-editorSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Every color, gradient, border, and shadow MUST be driven by CSS variables in index.css.
- Very specific: line 16
STRICT PROHIBITION: NEVER use raw direct color classes like text-white, bg-white, text-black, bg-black, bg-blue-500.
- Very specific: line 24
Use standardized cubic-bezier transitions (cubic-bezier(0.4, 0, 0.2, 1)) with durations between 150ms and 300ms.
- Distinctive: line 27
Test every component in both light and dark themes.
- Distinctive: line 28
Ensure a minimum contrast ratio of 4.5:1 for standard text and 3:1 for large headings (WCAG 2.2 AA).
- Very specific: line 34
Always define and customize the theme tokens inside index.css:
- Very specific: line 105
Use logical utilities (ms-*, me-*, start-*, end-*) instead of directional ml-*, mr-*, left-*, right-*.
- Very specific: line 145
Focus States: Every interactive element MUST have visible, high-contrast focus rings (focus-visible:ring-2 focus-visible:ring-ring …
- Very specific: line 149
Use semantic HTML tags (<header>, <nav>, <main>, <section>, <article>, <footer>).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Vercel-Inspired UI/UX Design Engineering Playbook
This playbook establishes the authoritative UI/UX design engineering rules, visual aesthetics, component composition patterns, typography hierarchy, and accessibility standards for building world-class, premium web interfaces inspired by Vercel Design Systems, Radix UI, and ShadCn UI.
1. Design Philosophy & Core Principles
- Semantic Design Tokens over Ad-Hoc Styling:
- Every color, gradient, border, and shadow MUST be driven by CSS variables in
index.css. - STRICT PROHIBITION: NEVER use raw direct color classes like
text-white,bg-white,text-black,bg-black,bg-blue-500. ALWAYS use semantic design tokens:text-foreground,bg-background,bg-card,text-primary,border-border,bg-accent.
- Every color, gradient, border, and shadow MUST be driven by CSS variables in
- Intentional White Space & Sub-Pixel Alignment:
- Layouts must breathe. Use standard spacing increments (4px, 8px, 16px, 24px, 32px, 48px, 64px).
- Align text baseline to grid, ensure sub-pixel rendering with
-webkit-font-smoothing: antialiased.
- Subtle Motion & Purposeful Micro-Animations:
- Animations should provide immediate tactile feedback, not distract.
- Use standardized cubic-bezier transitions (
cubic-bezier(0.4, 0, 0.2, 1)) with durations between 150ms and 300ms.
- Flawless Light & Dark Mode Contrast:
- Test every component in both light and dark themes.
- Ensure a minimum contrast ratio of 4.5:1 for standard text and 3:1 for large headings (WCAG 2.2 AA).
2. Semantic Design System Tokens (index.css)
Always define and customize the theme tokens inside index.css:
@layer base {
:root {
/* Light Mode Palette (HSL) */
--background: 0 0% 100%;
--foreground: 222 47% 11%;
--card: 0 0% 98%;
--card-foreground: 222 47% 11%;
--popover: 0 0% 100%;
--popover-foreground: 222 47% 11%;
--primary: 250 84% 60%;
--primary-glow: 250 84% 75%;
--primary-foreground: 210 40% 98%;
--secondary: 210 40% 96.1%;
--secondary-foreground: 222 47% 11.2%;
--muted: 210 40% 96.1%;
--muted-foreground: 215.4 16.3% 46.9%;
--accent: 320 89% 60%;
--accent-foreground: 222 47% 11.2%;
--destructive: 0 84.2% 60.2%;
--destructive-foreground: 210 40% 98%;
--border: 214.3 31.8% 91.4%;
--input: 214.3 31.8% 91.4%;
--ring: 250 84% 60%;
--radius: 0.75rem;
/* Gradients & Special Effects */
--gradient-hero: linear-gradient(135deg, hsl(var(--primary)), hsl(var(--accent)));
--gradient-subtle: linear-gradient(180deg, hsl(var(--background)), hsl(var(--card)));
--shadow-elegant: 0 10px 30px -10px hsl(var(--primary) / 0.2);
--shadow-glow: 0 0 35px hsl(var(--primary) / 0.25);
}
.dark {
/* Dark Mode Palette (Vercel Midnight) */
--background: 224 71% 4%;
--foreground: 213 31% 91%;
--card: 224 71% 7%;
--card-foreground: 213 31% 91%;
--popover: 224 71% 7%;
--popover-foreground: 213 31% 91%;
--primary: 250 84% 67%;
--primary-glow: 250 84% 80%;
--primary-foreground: 222 47% 11%;
--secondary: 215 27.9% 16.9%;
--secondary-foreground: 210 40% 98%;
--muted: 215 27.9% 16.9%;
--muted-foreground: 217.9 10.6% 64.9%;
--accent: 320 89% 65%;
--accent-foreground: 210 40% 98%;
--destructive: 0 62.8% 30.6%;
--destructive-foreground: 210 40% 98%;
--border: 215 27.9% 16.9%;
--input: 215 27.9% 16.9%;
--ring: 250 84% 67%;
}
}3. Typography & Responsive Scale Rules
- Font Hierarchy:
h1: Fluid sizing withtext-4xl sm:text-5xl lg:text-6xl, tracking tight (tracking-tight), font weightfont-extrabold.h2:text-2xl sm:text-3xl, tracking tight, font weightfont-semibold.body:text-baseortext-sm, text colortext-muted-foregroundortext-foreground.
- RTL & LTR Localization:
- Respect text alignment and flow when switching
dir="rtl"anddir="ltr". - Use logical utilities (
ms-*,me-*,start-*,end-*) instead of directionalml-*,mr-*,left-*,right-*.
- Respect text alignment and flow when switching
4. Component Composition & Variant Architecture
Using Class Variance Authority (cva) for reusable UI components:
import { cva, type VariantProps } from "class-variance-authority";
export const buttonVariants = cva(
"inline-flex items-center justify-center rounded-lg text-sm font-medium transition-all focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2 disabled:opacity-50 disabled:pointer-events-none active:scale-[0.98]",
{
variants: {
variant: {
default: "bg-primary text-primary-foreground hover:bg-primary/90 shadow-sm",
hero: "bg-gradient-to-r from-primary to-accent text-primary-foreground hover:opacity-95 shadow-lg shadow-primary/25",
outline: "border border-input bg-background hover:bg-accent hover:text-accent-foreground",
glass: "bg-background/60 backdrop-blur-md border border-border/50 text-foreground hover:bg-background/80 shadow-sm",
subtle: "bg-secondary text-secondary-foreground hover:bg-secondary/80",
},
size: {
sm: "h-9 px-3 rounded-md text-xs",
default: "h-10 py-2 px-4",
lg: "h-12 px-6 rounded-xl text-base",
},
},
defaultVariants: {
variant: "default",
size: "default",
},
}
);5. Accessibility (a11y) & Interactive States
- Focus States: Every interactive element MUST have visible, high-contrast focus rings (
focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2). - Keyboard Navigation: Full keyboard navigation support (
Tab,Enter,Space,Escape,Arrowkeys). - Screen Readers:
- Provide
aria-labeloraria-labelledbyon icon buttons and custom controls. - Use semantic HTML tags (
<header>,<nav>,<main>,<section>,<article>,<footer>).
- Provide
- Reduced Motion:
- Wrap intensive CSS animations in
@media (prefers-reduced-motion: reduce).
- Wrap intensive CSS animations in
6. Execution Workflow & Quality Verification
graph TD
A[1. Audit Design System Tokens in index.css] --> B[2. Check Color Tokens & Prohibit Raw Colors]
B --> C[3. Build Modular CVA Components]
C --> D[4. Verify Light & Dark Mode Contrast]
D --> E[5. Test Arabic RTL & English LTR]
E --> F[6. Audit Focus States & ARIA Attributes]
F --> G[7. Run Typecheck, Lint, Test & Production Build]7. UI/UX Release Checklist
- All colors defined as HSL CSS variables in
index.css. - Zero raw color classes (
text-white,bg-black,bg-blue-500) in component files. - Light and dark modes render with high contrast and zero invisible text.
- Components use logical CSS properties (
ms-*,me-*) for RTL/LTR parity. - Hover, active, focus, loading, empty, and error states present on all interactive components.
- All build and verification gates (
typecheck,lint,test,build) green.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

