
Web Design Guidelines
Generate or review UI so accessibility, contrast, forms, motion, and responsive patterns match a consolidated 100+ rule design ruleset.
Overview
Web Design Guidelines is an agent skill most often used in Build (also Ship review, Launch SEO-facing pages) that applies 100+ accessibility and UX rules when generating or reviewing UI code.
Install
npx skills add https://github.com/itallstartedwithaidea/agent-skills --skill web-design-guidelinesWhat is this skill?
- 100+ encoded rules across accessibility, forms, animation, typography, and navigation
- WCAG 2.2 AA–aligned contrast, focus, keyboard navigation, and alt-text defaults
- Covers dark mode, touch targets, i18n, images, performance, and platform HIG patterns
- Embeds a11y into generation—not a post-hoc compliance checkbox
- Usable for new page builds and design or code review passes
- 100+ rules covering accessibility, forms, animation, typography, navigation, and more
- Grounded in WCAG 2.2 AA requirements and platform HIG conventions
Adoption & trust: 1 installs on skills.sh; 18 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You ship UI quickly but keep missing focus states, contrast, form errors, and responsive details that hurt accessibility and polish.
Who is it for?
Solo builders using Claude Code, Cursor, or Codex who want agent-generated React/HTML/CSS to meet accessibility and design-quality bars by default.
Skip if: Pure brand-strategy or illustration-only work with no UI code, or teams that already enforce an unrelated exclusive design system with conflicting tokens.
When should I use this skill?
Generating UI code, reviewing designs, or building new pages where accessible, performant, consistent interfaces are required.
What do I get? / Deliverables
Generated or reviewed interfaces default to keyboard-navigable, contrast-safe, performant patterns aligned with WCAG-oriented and HIG-informed rules.
- UI code or patches aligned to the encoded guideline ruleset
- Review notes on accessibility, contrast, forms, and navigation quality
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Frontend is the canonical shelf because the skill’s primary job is shaping components and pages while code is being written. Frontend subphase fits UI generation, page builds, and component-level defaults agents apply during implementation.
Where it fits
Scaffold a settings page with visible focus rings, labeled inputs, and touch-friendly controls.
Run a pre-merge UI pass for contrast ratios, alt text, and motion-preference handling.
Polish marketing HTML for readable hierarchy, performant images, and navigable headers before publish.
How it compares
Use as an embedded rules engine during codegen and review—not instead of formal legal accessibility audits or dedicated design-tool mocks.
Common Questions / FAQ
Who is web-design-guidelines for?
Indie developers and small teams who rely on AI agents to build or refactor web and mobile-friendly UI and need consistent accessibility and UX quality.
When should I use web-design-guidelines?
During Build frontend work when scaffolding pages; during Ship review before merge; at Launch when polishing marketing or docs pages for readable, accessible layout.
Is web-design-guidelines safe to install?
It is documentation-driven procedural knowledge—confirm scope in SKILL.md and use the Security Audits panel on this page before adding third-party skill repos to your agent.
SKILL.md
READMESKILL.md - Web Design Guidelines
# Web Design Guidelines Part of [Agent Skills™](https://github.com/itallstartedwithaidea/agent-skills) by [googleadsagent.ai™](https://googleadsagent.ai) ## Description Web Design Guidelines encodes 100+ rules covering accessibility, focus states, forms, animation, typography, images, performance, navigation, dark mode, touch targets, and internationalization. The agent applies these rules when generating UI code, reviewing designs, or building new pages, producing interfaces that are accessible, performant, and visually consistent by default. These guidelines synthesize WCAG 2.2 AA requirements, platform-specific HIG conventions, and empirically validated UX patterns into a single actionable ruleset. Rather than treating accessibility as an afterthought or a compliance checkbox, these rules embed it into the generation process: every component is keyboard-navigable, every image has alt text, every color combination meets contrast ratios, and every interactive element has visible focus indicators. The rules extend beyond accessibility into comprehensive design quality: responsive typography scales, motion preferences, form validation patterns, image optimization, navigation hierarchy, dark mode implementation, touch-friendly sizing, and RTL/i18n support. The result is production-grade UI code that works for all users across all contexts. ## Use When - Generating new UI components or pages - Reviewing frontend code for accessibility compliance - Implementing dark mode or theme switching - Building forms with validation - Adding animations or transitions - Optimizing images and media - Supporting internationalization or RTL layouts ## How It Works ```mermaid graph TD A[UI Code Generation] --> B[Apply Rule Categories] B --> C[Accessibility: WCAG 2.2 AA] B --> D[Focus States: Visible + Logical] B --> E[Forms: Validation + Labels] B --> F[Animation: prefers-reduced-motion] B --> G[Typography: Fluid Scale] B --> H[Images: Responsive + Alt Text] B --> I[Performance: Lazy Load + CLS] B --> J[Navigation: Keyboard + Hierarchy] B --> K[Dark Mode: System Preference] B --> L[Touch: 44px Min Target] B --> M[i18n: RTL + Locale] C --> N[Validated UI Output] D --> N E --> N F --> N G --> N H --> N I --> N J --> N K --> N L --> N M --> N ``` Every generated component passes through all applicable rule categories before output. Rules are non-negotiable for accessibility; other categories are applied based on component type. ## Implementation ```css /* Focus: Always visible, high contrast */ :focus-visible { outline: 2px solid var(--color-focus); outline-offset: 2px; } /* Animation: Respect user preference */ @media (prefers-reduced-motion: reduce) { *, *::before, *::after { animation-duration: 0.01ms !important; transition-duration: 0.01ms !important; } } /* Typography: Fluid responsive scale */ :root { --step-0: clamp(1rem, 0.34vw + 0.91rem, 1.19rem); --step-1: clamp(1.2rem, 0.61vw + 1.07rem, 1.58rem); --step-2: clamp(1.44rem, 0.98vw + 1.24rem, 2.11rem); } /* Dark mode: System preference + manual toggle */ @media (prefers-color-scheme: dark) { :root:not([data-theme="light"]) { --bg: #0a0a0a; --fg: #ededed; } } /* Touch: Minimum 44px targets */ button, a, [role="button"] { min-height: 44px; min-width: 44px; } ``` ```tsx // Form: Accessible label + validation + error association function EmailField({ error }: { error?: string }) { const id = useId(); return ( <div> <label htmlFor={id}>Email address</label> <input id={id} type="email" aria-invalid={!!error} aria-describedby={error ? `${id}-error` : undefined