web-design-guidelines

Review web interface files against Web Interface Guidelines for compliance gaps.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/nishchaydev/emitra --skill web-design-guidelines-nishchaydev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-design-guidelines
Source: https://github.com/nishchaydev/emitra/tree/main/.agent/skills/web-design-guidelines
Command: npx skills add https://github.com/nishchaydev/emitra --skill web-design-guidelines-nishchaydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you catch accessibility, UX, and best-practice issues in a web UI before they harm users or reduce performance.

Core Features & Use Cases

  • Guideline-backed UI review: Fetches the latest Web Interface Guidelines and evaluates provided files against their rules.
  • Actionable findings output: Produces results in the terse file:line format so developers can fix issues quickly.
  • Targeted audits for common scenarios: Use it when someone asks to review UI, check accessibility, audit design/UX, or validate a site against best practices (e.g., after a UI refactor or before a release).

Quick Start

Use the web-design-guidelines skill to review the changed frontend files by providing a file path or pattern to audit for accessibility and best-practice 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 interface for accessibility and UX compliance?

To audit web interface accessibility and UX compliance, provide your frontend file paths or patterns to scan against the latest Web Interface Guidelines. The audit identifies specific violations and outputs actionable findings in a file:line format for quick resolution.

What is a UI review against web best practices and when do I need it?

A UI review against web best practices evaluates frontend code for accessibility, UX, and performance issues. You need it after a UI refactor or before a release to catch compliance gaps that could harm users or degrade site performance.

Does this accessibility check require any specific dependencies or components?

This accessibility check requires no external dependencies or components. It fetches fresh guideline rules directly from a specified source URL and scans your provided web interface files independently to report compliance findings.

How do I check website best practices before a release using a code audit?

To check website best practices before a release, run a code audit on your changed frontend files by providing a file path or pattern. The scan evaluates your code against fetched guidelines and reports UX and accessibility issues in a file:line format.

What's the best way to find UX and accessibility gaps in frontend files?

The best way to find UX and accessibility gaps is an automated guideline-backed code audit. It scans targeted frontend files against current Web Interface Guidelines and reports exact file:line locations for every identified compliance issue.

What format do the accessibility audit findings use for fixing code issues?

Accessibility audit findings use a terse file:line format. This allows developers to quickly locate and fix UX, accessibility, and best-practice compliance gaps within the reviewed web interface files without parsing verbose reports.