Web Design Guidelines

vercel-labs's avatarfrom vercel-labs
⭐16.3kstars🔀1.5kforks📁View on GitHub🕐Updated Jan 1, 1970
[Code Review]

When & Why to Use This Skill

This Claude skill automates the auditing of web interface code to ensure strict compliance with modern design systems and accessibility standards. By dynamically fetching the latest Vercel Web Interface Guidelines, it provides developers with precise, line-by-line feedback on UI consistency, UX best practices, and frontend quality, streamlining the transition from design to production-ready code.

Use Cases

  • Accessibility Auditing: Automatically scan React, Vue, or HTML files to identify and fix accessibility violations based on the latest web standards.
  • Design System Enforcement: Ensure that new UI components or page layouts strictly adhere to established web interface guidelines and brand consistency.
  • Automated UI Quality Assurance: Use as a pre-deployment check to audit UX and design implementation, catching visual or structural inconsistencies before they reach production.
  • Frontend Code Optimization: Review existing web interfaces against industry best practices to improve user experience and interface performance.
nameweb-design-guidelines
descriptionReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
authorvercel
version"1.0.0"
argument-hint<file-or-pattern>

Web Interface Guidelines

Review files for compliance with Web Interface Guidelines.

How It Works

  1. Fetch the latest guidelines from the source URL below
  2. Read the specified files (or prompt user for files/pattern)
  3. Check against all rules in the fetched guidelines
  4. Output findings in the terse file:line format

Guidelines Source

Fetch fresh guidelines before each review:

https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md

Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.

Usage

When a user provides a file or pattern argument:

  1. Fetch guidelines from the source URL above
  2. Read the specified files
  3. Apply all rules from the fetched guidelines
  4. Output findings using the format specified in the guidelines

If no files specified, ask the user which files to review.