WCAG 2.1 AA Accessibility Review
getcrew44/crew44
Audits a design or page against WCAG 2.1 AA for contrast, keyboard use, focus, labels, touch targets and screen reader behavior, with a severity-ranked report.
Reviews UI code against a written set of web interface rules covering accessibility, forms, animation and typography, and reports terse file:line findings.
Install Web Interface Guidelines Review
$ npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tech-leads-club/agent-skills web-design-guidelines --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'packages/skills-catalog/skills/(design)/web-design-guidelines' .claude/skills/web-design-guidelines && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "web-design-guidelines" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(design)/web-design-guidelines into .claude/skills/web-design-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "web-design-guidelines", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(design)/web-design-guidelinesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tech-leads-club/agent-skills web-design-guidelines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/'packages/skills-catalog/skills/(design)/web-design-guidelines' .agents/skills/web-design-guidelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "web-design-guidelines" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(design)/web-design-guidelines into .agents/skills/web-design-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "web-design-guidelines", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tech-leads-club/agent-skills web-design-guidelines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/'packages/skills-catalog/skills/(design)/web-design-guidelines' .cursor/skills/web-design-guidelines && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "web-design-guidelines" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(design)/web-design-guidelines into .cursor/skills/web-design-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "web-design-guidelines", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tech-leads-club/agent-skills.git --path 'packages/skills-catalog/skills/(design)/web-design-guidelines'--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tech-leads-club/agent-skills web-design-guidelines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/'packages/skills-catalog/skills/(design)/web-design-guidelines' .gemini/skills/web-design-guidelines && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "web-design-guidelines" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(design)/web-design-guidelines into .gemini/skills/web-design-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "web-design-guidelines", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tech-leads-club/agent-skills web-design-guidelinesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/'packages/skills-catalog/skills/(design)/web-design-guidelines' .github/skills/web-design-guidelines && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "web-design-guidelines" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(design)/web-design-guidelines into .github/skills/web-design-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "web-design-guidelines", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tech-leads-club/agent-skills web-design-guidelines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/'packages/skills-catalog/skills/(design)/web-design-guidelines' .opencode/skills/web-design-guidelines && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "web-design-guidelines" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(design)/web-design-guidelines into .opencode/skills/web-design-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "web-design-guidelines", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
web-design-guidelines- GitHub stars
- 7k
- Token cost
- ~509 tokens
- SKILL.md length
- 198 words
- Files
- 2 (incl. references)
- Skills in repo
- 74
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Reviews UI code against a written set of web interface rules covering accessibility, forms, animation and typography, and reports terse file:line findings.
- Works in 4 steps: Read the guidelines from… → Read the specified files (or prompt user… → Check against all rules in the guidelines → …
- Reviewing a component or page for accessibility problems
- SKILL.md covers How It Works, Guidelines Reference, Usage and Output Format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The agent reads the rule set in `references/guideline.md`, reads the files you name, checks them against every rule and prints its findings. If you give no files or pattern, it asks which ones to review.
The guidelines cover accessibility, focus states and keyboard use, forms, animation and reduced motion, typography, content overflow and empty states, images, performance, navigation and URL state, touch handling, dark mode, locale and i18n, hydration safety and common anti-patterns. Findings are grouped by file in clickable `file:line` form, stating the issue and its location and skipping explanations unless the fix is not obvious. Performance audits, SEO and full site audits are left to other skills.
When your agent uses it
- Reviewing a component or page for accessibility problems
- Checking forms for label, autocomplete and validation issues
- Auditing UI code for focus handling and keyboard support
- Getting a short list of design and interaction issues by file and line
Example prompts
- “Review src/components/Checkout.tsx against the web interface guidelines.”
- “Check the forms under app/ for accessibility and validation problems.”
- “Audit our dark mode and animation code for reduced-motion issues.”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read the guidelines from #[[file:references/guideline.md]]
- Read the specified files (or prompt user for files/pattern)
- Check against all rules in the guidelines
- Output findings in the terse file:line format
What it can do on your machine
Read from SKILL.md and the folder at commit 6df68d5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Web Interface Guidelines Review loads about 509 tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 198 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 198 words (~509 tokens).
“Review files for compliance with Web Interface Guidelines.”
- name
- web-design-guidelines
- metadata.author
- vercel
- metadata.version
- 1.0.0
- metadata.argument-hint
- <file-or-pattern>
Files
SKILL.md and 1 other file (references) in packages/skills-catalog/skills/(design)/web-design-guidelines of tech-leads-club/agent-skills.
- SKILL.md
- references/guideline.md
Open the folder on GitHubat commit 6df68d5
Compare with similar skills
Web Interface Guidelines Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Web Interface Guidelines Review this skilltech-leads-club/agent-skills | 7k | — | ~509 | Automated safety check: Pass | Custom licence | |
| WCAG 2.1 AA Accessibility Reviewgetcrew44/crew44 | 356 | — | ~741 | Automated safety check: Pass | MIT | |
| UI Reviewespennilsen/pi | 122 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Design Reviewpproenca/dot-skills | 215 | — | ~3.4k | Automated safety check: Pass | MIT | |
| UI Design ReviewMadAppGang/claude-code | 285 | — | ~2k | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None |
Similar skills
UI Review
espennilsen/pi
Review UI designs and implementations for accessibility, consistency, usability, and visual quality.
Design Review
pproenca/dot-skills
Structured UI design review — existing code (React/JSX, CSS, Tailwind) and, when behaviour matters, the running app in a real browser — reported as a prioritised Before / After / Why table.
UI Design Review
MadAppGang/claude-code
Prompting patterns and review templates for UI design analysis with Gemini multimodal capabilities.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
More from tech-leads-club/agent-skills
All 74 skills in this repoEvolutionary Modular Architecture
tech-leads-club/agent-skills
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
Excalidraw Diagram Studio
tech-leads-club/agent-skills
Generates Excalidraw diagram files from plain descriptions, choosing among flowcharts, mind maps, architecture, swimlane, class, sequence and ER diagrams.
Mermaid Studio
tech-leads-club/agent-skills
Creates, validates and renders Mermaid diagrams to SVG, PNG or ASCII, including C4 and AWS architecture-beta, flowcharts, sequence diagrams and ERDs.
AWS Cloud Advisor
tech-leads-club/agent-skills
Answers AWS architecture, security and service-selection questions by searching AWS documentation through MCP tools first, then adapting advice to your stack and team.
Harness Eval
tech-leads-club/agent-skills
Evaluates a repository's agent harness (AGENTS.md, rules, skills) for broken paths, redundant instructions and usefulness, and stops at reports.
NestJS Modular Monolith Architect
tech-leads-club/agent-skills
Designs scalable NestJS modular monoliths with domain-driven design, Clean Architecture layers and optional CQRS, defining bounded contexts and strict module boundaries.
Related
Categories
Questions about Web Interface Guidelines Review
What does Web Interface Guidelines Review do?
Reviews UI code against a written set of web interface rules covering accessibility, forms, animation and typography, and reports terse file:line findings. md`, reads the files you name, checks them against every rule and prints its findings. If you give no files or pattern, it asks which ones to review.
When should I use Web Interface Guidelines Review?
Web Interface Guidelines Review fits situations like: reviewing a component or page for accessibility problems; checking forms for label, autocomplete and validation issues; auditing UI code for focus handling and keyboard support; getting a short list of design and interaction issues by file and line.
How do I install Web Interface Guidelines Review in Claude Code?
Run `npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a claude-code`. Or copy the skill folder (packages/skills-catalog/skills/(design)/web-design-guidelines in tech-leads-club/agent-skills) into .claude/skills/web-design-guidelines in your project. Claude Code loads it when a task matches its description.
How do I install Web Interface Guidelines Review in Codex?
Run `npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a codex`. Or copy the skill folder (packages/skills-catalog/skills/(design)/web-design-guidelines in tech-leads-club/agent-skills) into .agents/skills/web-design-guidelines in your project. Codex loads it when a task matches its description.
Can I use Web Interface Guidelines Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/web-design-guidelines, .gemini/skills/web-design-guidelines, .github/skills/web-design-guidelines and .opencode/skills/web-design-guidelines in your project.
What does Web Interface Guidelines Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Web Interface Guidelines Review is instructions for the agent only.
Does Web Interface Guidelines Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Web Interface Guidelines Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Web Interface Guidelines Review use?
Web Interface Guidelines Review has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Web Interface Guidelines Review use?
About 509 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.
What are the alternatives to Web Interface Guidelines Review?
Skills that share tags, products or a category with Web Interface Guidelines Review: WCAG 2.1 AA Accessibility Review (getcrew44/crew44, 356 stars), UI Review (espennilsen/pi, 122 stars), Design Review (pproenca/dot-skills, 215 stars) and UI Design Review (MadAppGang/claude-code, 285 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Web Interface Guidelines Review?
tech-leads-club (a GitHub organization) maintains it in tech-leads-club/agent-skills, which has 7,045 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 9, 2026.
Source: tech-leads-club/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.