web-design
Review, fix, and enforce web UI quality standards for accessibility, visual design, and performance. Use when reviewing web component files for issues (`/web-design Button.tsx`), fixing accessibility or visual problems (`/web-design fix Button.tsx`), creating new components with quality constraints applied, or loading design constraints for the conversation (`/web-design`). Covers WCAG accessibility, interaction patterns, animation, layout, typography, and prevents common AI-generated UI issues. For web apps built with HTML/CSS/JS, React, Vue, Tailwind, etc.
Best use case
web-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Review, fix, and enforce web UI quality standards for accessibility, visual design, and performance. Use when reviewing web component files for issues (`/web-design Button.tsx`), fixing accessibility or visual problems (`/web-design fix Button.tsx`), creating new components with quality constraints applied, or loading design constraints for the conversation (`/web-design`). Covers WCAG accessibility, interaction patterns, animation, layout, typography, and prevents common AI-generated UI issues. For web apps built with HTML/CSS/JS, React, Vue, Tailwind, etc.
Teams using web-design should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/web-design/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How web-design Compares
| Feature / Agent | web-design | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Review, fix, and enforce web UI quality standards for accessibility, visual design, and performance. Use when reviewing web component files for issues (`/web-design Button.tsx`), fixing accessibility or visual problems (`/web-design fix Button.tsx`), creating new components with quality constraints applied, or loading design constraints for the conversation (`/web-design`). Covers WCAG accessibility, interaction patterns, animation, layout, typography, and prevents common AI-generated UI issues. For web apps built with HTML/CSS/JS, React, Vue, Tailwind, etc.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Web Design Review, fix, and enforce web UI quality standards. ## Invocation | Command | Behavior | |---------|----------| | `/web-design Component.tsx` | Review file for issues (default mode) | | `/web-design fix Component.tsx` | Apply minimal targeted fixes | | `/web-design` | Load constraints for this conversation | ## Mode Behavior ### Review Mode (default) When a file path is provided and the file exists, perform a full audit: 1. Read the file completely before making assessments 2. Check against all rules in `references/rules.md` 3. Output findings using the format below 4. Offer to fix issues if any are found **Review Output Format:** ``` ═══════════════════════════════════════════════════ DESIGN REVIEW: [filename] ═══════════════════════════════════════════════════ CRITICAL ([n] issues) ───────────────────── Line [n]: [issue description] [code snippet] Fix: [specific fix] Rule: [rule reference] SERIOUS ([n] issues) ──────────────────── ... MODERATE ([n] issues) ───────────────────── ... ═══════════════════════════════════════════════════ SUMMARY: [n] critical, [n] serious, [n] moderate ═══════════════════════════════════════════════════ ``` ### Fix Mode When invoked with `fix`, apply minimal targeted changes: 1. Prioritize critical issues first 2. Make surgical edits—do not refactor unrelated code 3. Prefer native HTML semantics before adding ARIA 4. Show each fix with before/after ### Create Mode When the file path doesn't exist: - If context is provided (user described what they want), create the component with all constraints applied - If no context, ask: "[filename] doesn't exist. What should this component do?" ### Enforce Mode When invoked without a file path, acknowledge constraints are loaded and apply them to all UI work in the conversation. ## Stack Defaults These are the opinionated defaults. Override only when the project uses different tools. | Category | Default | Notes | |----------|---------|-------| | Styling | Tailwind CSS | Use defaults unless custom values exist | | Animation (JS) | `motion/react` | Formerly framer-motion | | Animation (CSS) | `tw-animate-css` | For entrance/micro-animations | | Class logic | `cn` (`clsx` + `tailwind-merge`) | | | Primitives | Base UI, React Aria, or Radix | Never rebuild keyboard/focus behavior | **Primitive Rules:** - Use project's existing primitives first - Never mix primitive systems in the same interaction surface - Prefer Base UI for new primitives if stack-compatible - Never rebuild keyboard or focus behavior unless explicitly requested ## Rule Categories Rules are organized by priority. See `references/rules.md` for the complete list. | Priority | Category | Severity | |----------|----------|----------| | 1 | Accessible Names | Critical | | 2 | Keyboard Access | Critical | | 3 | Focus & Dialogs | Critical | | 4 | Interactions | High | | 5 | Forms | High | | 6 | Animation | Medium | | 7 | Layout | Medium | | 8 | Typography | Medium | | 9 | Performance | Medium | | 10 | Visual Polish | Low | ## Quick Reference ### Critical (must fix) - Icon-only buttons must have `aria-label` - All interactive elements reachable by Tab - Visible focus states (never `outline-none` without replacement) - Modals trap focus and restore on close - No `<div onClick>` for navigation—use `<a>` or `<button>` ### Anti-Slop Rules These prevent common AI-generated UI issues: - Never add animation unless explicitly requested - Never use gradients unless explicitly requested - Never use purple or multicolor gradients - Never use glow effects as primary affordances - Never exceed 200ms for interaction feedback - Never modify letter-spacing unless explicitly requested - Never use `h-screen`—use `h-dvh` - Never block paste in inputs - Empty states must have one clear next action ### Must Always Apply - `text-balance` for headings, `text-pretty` for body - `tabular-nums` for numeric data - Respect `prefers-reduced-motion` - Respect safe areas (`env(safe-area-inset-*)`) - Use AlertDialog for destructive actions - Show errors inline next to where action happens
Related Skills
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
vercel-web-design-guidelines
Reviews UI code for compliance with web interface best practices. Use when auditing accessibility, reviewing UI/UX patterns, checking performance, or improving web design quality. Triggers on "check my site", "audit design", "accessibility review", "UX best practices", or UI code review tasks. Covers 100+ rules for accessibility, performance, and user experience.
ui-ux-design
UI/UX design reference database. 50+ styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
ui-design
Opinionated constraints for building better interfaces with agents. Use when building UI components, implementing animations, designing layouts, reviewing frontend accessibility, or working with Tailwind CSS, motion/react, or accessible primitives like Radix/Base UI.
touchdesigner-api-lookup
Query local TouchDesigner API documentation and class references. Use this skill when the user asks about specific TouchDesigner operators, Python classes, parameters, or methods.
tools-ui-frontend-design
Create distinctive, production-grade frontend interfaces grounded in this repo's design system. Use when asked to build web components, pages, or applications. Combines bold creative direction with token-constrained implementation.
thehub-design-system
Senior PHP/Frontend engineer for TheHUB - Swedish cycling competition platform on Uppsala WebHotell. Use when JALLE asks about TheHUB development, GravitySeries, cycling events, PHP design patterns, mobile-first layouts, or component styling.
system-design
Comprehensive system design skill for creating professional software architecture specifications. Use this skill when asked to design systems (e.g., "Design a chat application", "Design an e-commerce platform", "Create system architecture for X"). Generates complete technical specifications with architecture diagrams, database schemas, API designs, scalability plans, security considerations, and deployment strategies. Creates organized spec folders with all documentation following professional software engineering standards, from high-level overview down to detailed implementation specifications.
system-design-patterns
System design patterns for scalability, reliability, and performance. Use when: (1) designing distributed systems, (2) planning for scale, (3) making architecture decisions, (4) evaluating trade-offs.
mobile-first-design-rules
Focuses on rules and best practices for mobile-first design and responsive typography using tailwind.
mobile-design
Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches pr...
http-api-design
Design and implement lightweight, ergonomic JSON HTTP APIs for machine-to-machine communication. Use this skill whenever the user is designing API endpoints, writing OpenAPI specs, building REST or HTTP API routes, defining request/response schemas, implementing error handling for APIs, or discussing API contracts.