web-design-guidelines

Review frontend code against web interface guidelines and return file-line findings.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/jaimedhenriques/finsyt --skill web-design-guidelines-jaimedhenriques
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-design-guidelines
Source: https://github.com/jaimedhenriques/finsyt/tree/main/.agents/skills/web-design-guidelines
Command: npx skills add https://github.com/jaimedhenriques/finsyt --skill web-design-guidelines-jaimedhenriques

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly identify UI and UX issues that conflict with modern Web Interface Guidelines, reducing manual review effort and preventing avoidable accessibility and design regressions.

Core Features & Use Cases

  • Guideline Compliance Review: Checks frontend code against the latest web interface rules.
  • Accessibility and UX Audits: Spots issues that affect usability, clarity, and inclusive design.
  • Terse Findings Output: Returns review results in a compact file:line format for fast triage.
  • Use Case: A developer submits a component or page and uses this Skill to verify that the interface follows current best practices before merging changes.

Quick Start

Review the specified UI files against the latest web interface guidelines and return only the compliance 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 violations?

To audit frontend code for accessibility and web design violations, submit your UI files to be fetched against the latest web interface guidelines. The tool compares every rule against your code and returns terse file-line findings for fast triage.

Can I check UI components against web interface guidelines before merging changes?

Yes, you can check UI components against web interface guidelines before merging by running a review task on the specified files. It identifies design and accessibility regressions, returning compact file:line findings to verify compliance.

What is the best way to perform a UX audit on frontend code?

The best way to perform a UX audit on frontend code is comparing every rule of the latest web interface guidelines against your provided files. This process spots issues affecting usability and inclusive design, returning terse findings for quick triage.

Does this UI review work with specific file patterns or only full pages?

This UI review works with specified files or file patterns, not just full pages. It fetches the latest guideline source and applies the rules across the provided frontend code, returning compact file-line findings for any violations found.

How do I get fast triage results from an accessibility audit?

To get fast triage results from an accessibility audit, the tool returns findings in a terse file:line format. This compact output allows you to quickly identify and resolve UI code that violates modern web interface design best practices.

Why does my UI review return terse file-line findings instead of detailed explanations?

Your UI review returns terse file-line findings instead of detailed explanations to enable fast triage of accessibility and design regressions. This compact format highlights code violating web interface guidelines for quick developer action.