Awesome-omni-skill web-design-guidelines

Review UI code for Web Interface Guidelines compliance. Use when asked

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/web-design-guidelines-gensart-projs" ~/.claude/skills/diegosouzapw-awesome-omni-skill-web-design-guidelines-414d64 && rm -rf "$T"

manifest: skills/development/web-design-guidelines-gensart-projs/SKILL.md

source content

Web Interface Guidelines

Review files for compliance with Web Interface Guidelines.

How It Works

Fetch the latest guidelines from the source URL below
Read the specified files (or prompt user for files/pattern)
Check against all rules in the fetched guidelines
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:

Fetch guidelines from the source URL above
Read the specified files
Apply all rules from the fetched guidelines
Output findings using the format specified in the guidelines

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

Related Skills

Skill	When to Use
frontend-design	Before coding - Learn design principles (color, typography, UX psychology)
web-design-guidelines (this)	After coding - Audit for accessibility, performance, and best practices

Design Workflow

1. DESIGN   → Read frontend-design principles
2. CODE     → Implement the design
3. AUDIT    → Run web-design-guidelines review ← YOU ARE HERE
4. FIX      → Address findings from audit