web-design-guidelines · tech-leads-club — Claude Code skill: review UI guidelines
web-design-guidelines reviews UI components against Web Interface Guidelines. Catches accessibility issues, missing form labels, and hydration pitfalls directly in your code.
MIT ★ 7,191 updated 2026-10-24
npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a claude-codeWhat web-design-guidelines does
The skill evaluates component code against rules compiled in references/guideline.md. It inspects semantic HTML, ARIA attributes, keyboard navigation, and visible focus states. Checks also cover form autocompletion, hydration safety, dark mode theming, and reduced motion settings.
Feedback comes back grouped by file in a terse file:line format that works smoothly with VS Code. Claude outputs the exact location and the detected issue. Long explanations are skipped unless the underlying fix is complex.
This skill targets interface patterns exclusively. It will not benchmark Core Web Vitals or audit search engine metadata.
What it helps with
- catch missing ARIA attributes and keyboard focus traps
- flag hydration safety issues in UI components
- verify input autocompletion and validation labels in forms
- detect missing reduced-motion alternatives for animations
Example prompts for the agent
- Review my UI in src/components/Navigation.tsx against design guidelines
- Check accessibility and form labels in src/components/AuthModal.tsx
- Audit design patterns across src/components/**/*.tsx
How to install web-design-guidelines
1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a claude-code2Manually: put the files in place
~/.claude/skills/web-design-guidelines/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/web-design-guidelines/
1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a codex2Manually: put the files in place
.agents/skills/web-design-guidelines/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a cursor2Manually: put the files in place
.cursor/skills/web-design-guidelines/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tech-leads-club/agent-skills 'packages/skills-catalog/skills/(design)/web-design-guidelines'2Manually: put the files in place
.github/skills/web-design-guidelines/SKILL.md1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a gemini-cli2Platform CLI
gemini skills install https://github.com/tech-leads-club/agent-skills --path 'packages/skills-catalog/skills/(design)/web-design-guidelines'Manually: put the files in place
.devin/skills/web-design-guidelines/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about web-design-guidelines
How to install web-design-guidelines in Claude Code?
Run npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a claude-code. Alternatively, place the skill definition file at ~/.claude/skills/web-design-guidelines/SKILL.md.
What does the web-design-guidelines skill do?
It scans specified UI files against Web Interface Guidelines and reports issues covering accessibility, touch targets, dark mode, typography, and hydration safety.
Does web-design-guidelines perform SEO or performance audits?
No, it focuses strictly on visual styling and interaction design. The instructions explicitly point to dedicated tools like core-web-vitals and seo for performance and search audits.
Source text
SKILL.md · MIT
--- name: web-design-guidelines description: 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". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit). metadata: author: vercel version: '1.0.0' argument-hint: <file-or-pattern> --- # Web Interface Guidelines Review files for compliance with Web Interface Guidelines. ## How It Works 1. Read the guidelines from `#[[file:references/guideline.md]]` 2. Read the specified files (or prompt user for files/pattern) 3. Check against all rules in the guidelines 4. Output findings in the terse `file:line` format ## Guidelines Reference All rules and output format instructions are in: ``` #[[file:references/guideline.md]] ``` The guidelines cover: - Accessibility (ARIA, semantic HTML, keyboard navigation) - Focus states and keyboard interaction - Forms (autocomplete, validation, labels) - Animation (reduced motion, performance) - Typography (proper characters, number formatting) - Content handling (overflow, empty states) - Images (dimensions, lazy loading) - Performance (virtualization, DOM reads) - Navigation & state (URL sync, deep linking) - Touch & interaction (tap delays, safe areas) - Dark mode & theming - Locale & i18n - Hydration safety - Common anti-patterns to flag ## Usage When a user provides a file or pattern argument: 1. Read the guidelines from `references/guideline.md` 2. Read the specified files 3. Apply all rules from the guidelines 4. Output findings using the format specified in the guidelines If no files specified, ask the user which files to review. ## Output Format Follow the format in the guidelines: - Group findings by file - Use `file:line` format (VS Code clickable) - Terse, high signal-to-noise - State issue + location - Skip explanation unless fix is non-obvious
© vercel · MIT · tech-leads-club/agent-skills
Similar skills
All skills for Frontend and UI →web-design-guidelines by other authors comes first.