web-design-guidelines

Review web UI code against Web Interface Guidelines with file:line findings.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gleeb/ai-registry --skill web-design-guidelines-gleeb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-design-guidelines
Source: https://github.com/gleeb/ai-registry/tree/main/.agents/skills/web-design-guidelines
Command: npx skills add https://github.com/gleeb/ai-registry --skill web-design-guidelines-gleeb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you evaluate whether your web UI complies with Web Interface Guidelines so you can catch accessibility and best-practice issues early.

Core Features & Use Cases

  • Guideline-driven UI review: Fetches the latest official guidelines and applies all rules to the files you specify.
  • Fast, traceable results: Reports findings in a terse file:line format to make fixes straightforward.
  • Flexible input: Works with a file path, or a pattern, and can prompt for files if none are provided.

Quick Start

Ask the AI to review your frontend files by telling it which file or pattern to check, such as “Review my UI files under src for Web Interface Guidelines compliance.”

Frequently Asked Questions about web-design-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my web UI code for accessibility compliance?

An accessibility audit checks your frontend files against the latest Web Interface Guidelines by applying all rules to specified file paths or patterns, producing deterministic file:line findings for straightforward fixes.

What is the file:line reporting format for UX audits?

The file:line reporting format outputs deterministic findings that pinpoint exact locations of accessibility and best-practice issues in your code. This terse format makes fixes straightforward by providing direct file and line number references for each guideline violation.

Can I review multiple frontend files using a pattern for UX best-practice checks?

Yes, you can review multiple frontend files using a file path or pattern for UX best-practice checks. If no files are specified, the review process can prompt you to provide the target files or patterns to evaluate against the Web Interface Guidelines.

Does this web UI review require fetching external guidelines?

Yes, this web UI review requires fresh guideline retrieval from a provided command URL. It fetches the latest official Web Interface Guidelines rule set and applies those rules to your specified files to ensure compliance checks are always up-to-date.

What is the best way to check site compliance validation for modern web projects?

The best way to check site compliance validation is fetching the latest official Web Interface Guidelines and applying all rules directly to your frontend files, which generates deterministic file:line findings to catch accessibility and best-practice issues early in modern web projects.