skills.rest
marcojsmith
marcojsmithCOMMUNITY
Explore all skills by this author →
GitHub

web-design-guidelines

Audit web interfaces against fetched Web Interface Guidelines and emit file:line findings.

2|Updated Feb 12, 2026
Search Tags:#linting#accessibility#frontend#web-design#design-guidelines#ui-review
One-click install
npx skills add https://github.com/marcojsmith/AgriBid --skill web-design-guidelines-marcojsmith
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-design-guidelines
Source: https://github.com/marcojsmith/AgriBid/tree/main/.agent/skills/web-design-guidelines
Command: npx skills add https://github.com/marcojsmith/AgriBid --skill web-design-guidelines-marcojsmith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps ensure UI code adheres to current Web Interface Guidelines, catching deviations early to improve accessibility, usability, and visual consistency.

Core Features & Use Cases

  • Guideline-driven review: Checks UI components against the latest guidelines fetched at runtime.
  • Pattern-based evaluation: Applies rules to specified files or file patterns.
  • Use Case: When shipping a new UI component, run this to surface accessibility and design-consistency issues before merge.

Quick Start

Run a review of the target UI files against the latest Web Interface Guidelines to surface any accessibility or consistency issues.

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 UI code for web design guideline compliance?▼

To audit UI code for design guideline compliance, run a review against the latest Web Interface Guidelines to validate specified files or patterns and emit file:line findings for accessibility and consistency issues.

What is design guideline linting for frontend web interfaces?▼

Design guideline linting for frontend web interfaces is the process of fetching current rules and validating targeted UI files against them to catch accessibility, usability, and visual consistency deviations early.

Can I check specific UI files or patterns for accessibility issues before merge?▼

Yes, you can check specific UI files or patterns for accessibility issues by applying rules to targeted components, which surfaces design-consistency deviations before you merge new frontend code.

What's the best way to ensure UI consistency across frontend projects?▼

The best way to ensure UI consistency across frontend projects is to run pattern-based evaluations against fetched Web Interface Guidelines, validating your UI code to surface deviations as file:line findings.

Do I need to configure dependencies to run a UI review?▼

No dependencies are required to run a UI review. The process fetches the latest rules at runtime, reads your specified frontend files, and validates them against established design guidelines without external setup.

When should I run an accessibility and design-consistency check on my UI components?▼

You should run an accessibility and design-consistency check when shipping a new UI component, as this surfaces deviations from current Web Interface Guidelines early to improve usability and visual consistency.

Related Skills

Explore More Design & Creative Skills→
Kilo-OrgKilo-Org
166

web-design-guidelines

Evaluate UI code against Web Interface Guidelines for accessibility and design compliance.

Official
Intermediate
MattRibMattRib

web-design-guidelines

Identify UI code violating Web Interface Guidelines and report file:line findings.

Community
Basic
t-stringst-strings

Global Validation

Enforce centralized validation standards across repository code and CI pipelines.

Official
Basic
aberrantCodeaberrantCode
1

web-design-guidelines

Audit UI code against Vercel's Web Interface Guidelines with file:line findings.

Community
Intermediate