web-design-guidelines

Check web interface source files against Web Interface Guidelines rules.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/leexb-wp21-prog/Azure-Ticket-Helpdesk --skill web-design-guidelines-leexb-wp21-prog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-design-guidelines
Source: https://github.com/leexb-wp21-prog/Azure-Ticket-Helpdesk/tree/main/.cursor/skills/skills-main/skills-main/skills/web-design-guidelines
Command: npx skills add https://github.com/leexb-wp21-prog/Azure-Ticket-Helpdesk --skill web-design-guidelines-leexb-wp21-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify UI and accessibility compliance issues by checking your web interface code against an up-to-date Web Interface Guidelines rule set.

Core Features & Use Cases

  • Guideline-powered UI review: Fetches the latest rules from the official source and applies them consistently to your provided files.
  • Targeted file or pattern scanning: Reviews specific paths or prompts for what to check when no inputs are provided.
  • Actionable reporting: Produces findings in a terse file:line format so you can quickly locate and fix issues.

Use case example: You want to audit a React/TypeScript front end for accessibility and best-practice violations before a release, and you need precise locations for fixes.

Quick Start

Ask the skill to review your UI files matching a path pattern like src/pages/**/*.tsx.

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 interface source files for accessibility compliance?

To audit web interface source files for accessibility compliance, provide specific file paths or glob patterns to the skill. It fetches the latest Web Interface Guidelines rules and reports UX and accessibility violations in a precise file:line format.

Can I scan specific UI directories or do I need to provide individual files for a UX review?

You can target specific UI directories for a UX review by providing glob patterns like src/pages/**/*.tsx. The skill scans matching files against design best practices and accessibility rules, reporting any compliance issues found.

What format do accessibility audit results use so I can locate issues in my code?

Accessibility audit results use a terse file:line format so you can quickly locate and fix issues in your code. This actionable reporting pinpoints exact source file locations for every UX and compliance violation detected.

Does the accessibility rule checking use a static rule set or fetch fresh web UI guidelines?

The accessibility rule checking fetches fresh web UI guidelines from a provided command URL before running any rule checks. This ensures your source files are always evaluated against the latest design and compliance standards.

What do I need to run a design audit on my React or TypeScript front end before release?

To run a design audit on your React or TypeScript front end, you need your source file paths and an environment that supports fetching guideline content from a URL. The skill checks the provided files and outputs best-practice compliance findings.

Are there limitations when checking site-wide best practices across a large web project?

A limitation when checking site-wide best practices is that the skill requires file paths or patterns as input and must fetch fresh guideline content from a URL before scanning. It does not autonomously discover project files without explicit path guidance.