web-design-guidelines

web-design-guidelines is a skill for Claude Code from AsyrafHussin/agent-skills. It costs 71 tokens per session (1,964 once invoked), scanned A, original, MIT.

A set of web interface guidelines covering accessibility, user experience, semantic HTML, keyboard use, forms, and performance. It can also audit code against WCAG, the widely used rules for making websites usable by people with disabilities.

In plain words
What is it for?
Use it to review UI code, check accessibility, audit forms, or verify web design practices. It supports React, Vue, Laravel Blade, and static HTML projects.
Why use it?
It helps find interface problems that may block keyboard users, screen-reader users, or people with other access needs. Audit results identify the file, line, issue, and suggested fix.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions AGENTS.md.

not rated 75repo +3 16d ago A scan Socket: passSnyk: passSkillSpector: pass 71 tokens original MIT

Good fit Use it to review UI code, check accessibility, audit forms, or verify web design practices. It supports React, Vue, Laravel Blade, and static HTML projects.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/asyrafhussin/agent-skills/web-design-guidelines
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add AsyrafHussin/agent-skills --skill web-design-guidelines
Clone the repo
git clone --depth 1 https://github.com/AsyrafHussin/agent-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for web-design-guidelines

README.md
[![agentmods](https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/web-design-guidelines/github.svg)](https://agentmods.dev/skills/asyrafhussin/agent-skills/web-design-guidelines)
Your own site
<a href="https://agentmods.dev/skills/asyrafhussin/agent-skills/web-design-guidelines"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/web-design-guidelines/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for web-design-guidelines

Your own site · 80×15
<a href="https://agentmods.dev/skills/asyrafhussin/agent-skills/web-design-guidelines"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/web-design-guidelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,964 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 26 Mar 2026
  • Snyk pass 26 Mar 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.01964
Opus 5 $0.00036 $0.00982
Sonnet 5 $0.00014 $0.00393
Haiku 4.5 $0.00007 $0.00196

Measured 12d ago against content hash 01bd9762a820, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

web-design-guidelines scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/web-design-guidelines/SKILL.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Web Design Guidelines

WCAG accessibility, semantic HTML, keyboard navigation, forms, and performance patterns for inclusive web interfaces. Contains 23 rules across 4 categories. Supports both coding reference and audit mode.

Metadata

  • Version: 2.1.0
  • Rule Count: 23 rules across 4 categories
  • License: MIT

How to Audit

When the user asks to "audit accessibility", "check WCAG compliance", or "review accessibility" — run the checklist below against their codebase.

Step 1: Determine Scope

  • If arguments provided ($ARGUMENTS): audit only those files or components
  • If no arguments: audit all UI components and pages in the codebase

Step 2: Detect Stack

Check the project for:

  • .tsx/.jsx files → React
  • .vue files → Vue
  • .blade.php files → Laravel Blade
  • .html files → Static HTML

Step 3: Run Accessibility Checklist

Work through every item below. For each, output:

  • PASS — brief confirmation of what was verified
  • FAIL — exact file:line, description of the issue, and fix recommendation
  • N/A — if the check does not apply to this project
Semantic HTML & Structure
  • Pages use semantic elements (<header>, <main>, <nav>, <footer>, <article>, <section>) — not <div> soup
  • Heading hierarchy is sequential (h1h2h3) — no skipped levels
  • One <h1> per page
  • Skip link exists to bypass navigation (<a href="#main-content">Skip to content</a>)
  • Landmark regions are labelled when duplicated (aria-label on multiple <nav> elements)
Keyboard Navigation
  • All interactive elements are reachable via Tab key
  • Focus order follows visual order (no positive tabindex values)
  • Focus indicator is visible on all focusable elements (not removed with outline: none without replacement)
  • Modal dialogs trap focus and return focus on close
  • Custom components (dropdowns, tabs, accordions) support expected keyboard patterns (Arrow keys, Escape, Enter)

Read the full file on GitHub · 211 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 211 lines · 71 tokens per session scan A 01bd9762a820

Subscribe to this mod's changes

web-design-guidelines is a skill published in the GitHub repository AsyrafHussin/agent-skills (75 stars, last pushed 16d ago), licensed MIT. It adds 71 tokens to every session and 1,964 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

recipe-front-design

Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval.

shinpr/claude-code-workflows · 22 tokens

recipe-front-adjust

Adjust an already-implemented UI in-session with verification against the design source.

shinpr/claude-code-workflows · 18 tokens

ring:validating-ux-completeness

Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer…

LerianStudio/ring · 113 tokens

ring:checking-frontend-quality

Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for…

LerianStudio/ring · 102 tokens

recipe-front-adjust

Adjust an implemented UI with focused evidence, verification, and quality checks.

shinpr/codex-workflows · 18 tokens

fidelity-gate

Build a UI against a frozen visual reference without drift - an inventory extracted before any code, a relics list, and a gate that MEASURES computed styles on a fixture carrying the reference's own data. Use when a mockup, design spec or screenshot is the contract.

jjanczur/tyran · 56 tokens