Web design guidelines

Skill karim-bhalwani/agent-skills-collection/skills/web-design-guidelines

Review UI code for Web Interface Guidelines compliance. Use when reviewing UI code, checking accessibility standards, auditing design consistency, or validating sites against best practices.From its SKILL.md

Install

npx -y skills add karim-bhalwani/agent-skills-collection --skill web-design-guidelines

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.2 KB, 569 tokens by cl100k_base, as published. Nobody here has run it

Web Interface Guidelines

Review files for compliance with Web Interface Guidelines.

How It Works

Fetch the latest guidelines from the source URL below
Read the specified files (or prompt user for files/pattern)
Check against all rules in the fetched guidelines
Output findings in the terse file:line format

Guidelines Source

Fetch fresh guidelines before each review:

https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md

Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.

Usage

When a user provides a file or pattern argument:

Fetch guidelines from the source URL above
Read the specified files
Apply all rules from the fetched guidelines
Output findings using the format specified in the guidelines

If no files specified, ask the user which files to review.

Outputs & Deliverables

Primary Output: Accessibility and design review findings in file:line format and a short remediation list
Secondary Output: Suggested code snippets or CSS fixes for small violations
Success Criteria: No critical accessibility failures and clear remediation steps for others
Quality Gate: implementer review for fixes prior to merge

Constraints

Technical Constraints: Do not modify source files automatically; produce recommended fixes only
Scope Constraints: Focus on UI guidelines and accessibility; visual design approvals are separate
Governance Constraints: Use latest guidelines from the canonical source before each review

Common Pitfalls

Stale Guidelines: Using local cached guidelines instead of fetching fresh ones. Always fetch from the canonical source before each review.
Skipping Accessibility: Checking only visual design, not keyboard navigation or screen reader support. Accessibility is mandatory, not optional.
Ignoring Contrast Ratios: Visual text looks fine but fails WCAG contrast requirements. Always validate color contrasts programmatically.
Missing Responsive Testing: UI looks good on desktop but breaks on mobile. Test at multiple breakpoints.
Not Suggesting Fixes: Reporting problems without showing how to fix them. Always provide remediation code snippets.
Vague Findings: "Design looks off" instead of specific violations. Reference exact lines and rules.

Integration Points

Phase	Input From	Output To	Context
Review Request	UI code files	Guidelines fetch	Retrieve canonical guidelines from source
Analysis	Code patterns and styles	Findings report	Identify violations against guidelines
Remediation	Violations found	`implementer`	Provide code examples for fixes
Merge Gate	UI changes complete	QA approval	No critical accessibility issues before merge

What ships with it: 1 file

78 B alongside SKILL.md

references/

color_tokens.md78 B