web-design-guidelines

Review UI code against current web interface guidelines and report file:line violations.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/kolodach/intervies --skill web-design-guidelines-kolodach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-design-guidelines
Source: https://github.com/kolodach/intervies/tree/main/.agents/skills/web-design-guidelines
Command: npx skills add https://github.com/kolodach/intervies --skill web-design-guidelines-kolodach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams catch UI, accessibility, and interaction issues early by reviewing interface code against a consistent set of web design rules.

Core Features & Use Cases

  • Guideline Compliance Review: Checks files against the latest published web interface guidelines.
  • Frontend Audit Support: Useful for pages, components, and design-system work where layout, accessibility, and UX details matter.
  • Terse Reporting: Returns findings in file:line format so developers can fix issues quickly.
  • Example: Use it before merging a new page or component to catch visual and interaction regressions.

Quick Start

Review the attached UI files against the latest web interface guidelines and return only terse file:line findings.

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 frontend code for web design and accessibility compliance?

You audit frontend code by reviewing UI files against the latest web interface guidelines to catch accessibility, usability, and interaction issues early. This Skill returns findings in a terse file:line format so developers can quickly fix violations.

What's the best way to run a UX audit on existing UI components?

Running a UX audit on UI components involves fetching the current web design guideline source and scanning component code for layout and interaction violations. The process reports specific accessibility and usability issues in a terse file:line format.

Can I use this to review a design-system implementation before merging?

Yes, you can review design-system implementations before merging by checking pages and components against current web interface guidelines. It catches visual and interaction regressions by returning terse file:line findings for quick developer fixes.

Do I need to provide the web design guidelines for the UI review?

Yes, the UI review requires fetching the current web design guideline source to check frontend components against the latest accessibility and usability rules. This ensures the audit reports violations based on up-to-date interaction standards.

Why does my frontend component pass visual checks but fail accessibility guidelines?

Frontend components often fail accessibility guidelines because visual checks do not verify interaction details or screen reader support. Auditing interface code against current web design rules identifies these hidden usability violations in a terse file:line format.

Does this UI review work for full pages or only individual components?

This UI review works for both full pages and individual frontend components. It applies guideline compliance checks to any design-system implementation, reporting accessibility and interaction violations in a terse file:line format.