skills.rest
iBz-04
iBz-04COMMUNITY
Explore all skills by this author →
WebsiteGitHub

web-design-guidelines

Review web UI source files against Web Interface Guidelines for accessibility and design issues.

63|12|Updated Mar 9, 2026
Search Tags:#accessibility#compliance#design review#web ui#ux audit#file line findings
One-click install
npx skills add https://github.com/iBz-04/gloamy --skill web-design-guidelines-ibz-04
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-design-guidelines
Source: https://github.com/iBz-04/gloamy/tree/main/.agents/skills/web-design-guidelines
Command: npx skills add https://github.com/iBz-04/gloamy --skill web-design-guidelines-ibz-04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you find UI, accessibility, and UX issues by checking your web interface code against a maintained set of Web Interface Guidelines.

Core Features & Use Cases

  • Guidelines-to-code compliance review: Compares your provided files to the latest rule set fetched before each audit.
  • Pattern-based scanning: Lets you review specific files or broader matches using the argument hint.
  • Actionable findings output: Reports issues in a terse file:line format so you can quickly locate and fix problems.

Quick Start

Ask it to review the frontend files you suspect have accessibility or design guideline problems.

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

To audit web UI source files for accessibility compliance, the Skill fetches the latest Web Interface Guidelines, reads the requested files, and outputs accessibility and design inconsistencies in a file:line format.

Can I review specific frontend files or do I need to scan an entire project for UX issues?▼

You can review specific frontend files or broader matches using pattern-based scanning. The Skill accepts file arguments or pattern-matched sets to locate UX issues, applying the fetched guideline rules only to the requested scope.

What format are the accessibility and design review findings reported in?▼

The accessibility and design review findings are reported in a terse file:line format. This output structure helps you quickly locate and fix UI inconsistencies directly in your web interface code.

Does the UX audit use a static rule set or fetch updated web interface guidelines?▼

The UX audit fetches the latest guideline rules from a provided command.md URL before each review. This ensures your web UI source files are checked against the most current Web Interface Guidelines.

When do I need to run a design review against best practices?▼

You need to run a design review against best practices when you suspect your frontend files have accessibility or UX issues. Requesting an audit via phrases like review my UI surfaces design inconsistencies quickly.

What are the limitations of pattern-based scanning for design compliance?▼

The limitation of pattern-based scanning for design compliance is that it requires accurately specifying file paths or patterns. It relies on fetching external guideline rules, meaning audits depend on the command.md URL.

Related Skills

Explore More Design & Creative Skills→
KaranKathur06KaranKathur06

web-design-guidelines

Review web UI source files against fetched Web Interface Guidelines.

Community
Intermediate
ahiendzahiendz
3

web-design-guidelines

Fetch Web Interface Guidelines and report UI compliance issues in file:line format.

Community
Intermediate
Jia-Hong-PengJia-Hong-Peng

design-review

Detect visual design inconsistencies and commit atomic fixes with screenshots.

Community
Advanced
kindfi-orgkindfi-org
19

web-design-guidelines

Assess UI code against Web Interface Guidelines for accessibility and design issues.

Official
Intermediate