Web Design Guidelines
- 830 installs
- 44k repo stars
- Updated July 27, 2026
- sickn33/antigravity-awesome-skills
Web Design Guidelines is a Claude Code skill that automatically reviews frontend files against the official Vercel Web Interface Guidelines and outputs terse file:line compliance findings before UI commits.
About
Web Design Guidelines is a frontend review skill from sickn33/antigravity-awesome-skills that checks files for compliance with Vercel Web Interface Guidelines. On each run it fetches the latest rules from raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md via WebFetch, reads specified files or user-provided patterns, evaluates every guideline rule, and outputs findings in terse file:line format. The skill is marked risk safe and sourced from the community with a 2026-02-27 date_added entry. Developers reach for Web Design Guidelines before committing UI changes when they want an agent-driven pass against Vercel's official interface standards rather than manual checklist review. Fresh guideline fetching ensures reviews reflect upstream rule updates.
- Automatically fetches the latest guidelines from the official command.md source before every run
- Reviews specified files or glob patterns for full compliance with Web Interface Guidelines
- Outputs findings in the exact terse file:line format required by the guidelines
- Asks for clarification when no files or patterns are provided
- Enforces consistent, high-quality web UI patterns across every project
Web Design Guidelines by the numbers
- 830 all-time installs (skills.sh)
- +24 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #472 of 1,896 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill web-design-guidelinesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 830 |
|---|---|
| repo stars | ★ 44k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | sickn33/antigravity-awesome-skills ↗ |
How do you review UI against Vercel guidelines?
Automatically review frontend files against the official Vercel Web Interface Guidelines before committing UI changes.
Who is it for?
Frontend developers committing UI changes who want an automated Vercel Web Interface Guidelines review with file:line output.
Skip if: Backend-only changes, visual design critique unrelated to interface guidelines, or teams not targeting Vercel's Web Interface Guidelines standard.
When should I use this skill?
A developer requests a Web Interface Guidelines review, names frontend files to check, or prepares UI changes for commit.
What you get
Terse file:line guideline violation reports fetched from the latest Vercel Web Interface Guidelines command.md.
- file:line guideline report
By the numbers
- Fetches guidelines from vercel-labs/web-interface-guidelines main/command.md on each review run
Files
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.mdUse 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.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related skills
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.698k164k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.486k29.4k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst382k15.8k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k470
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.284k66.9k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.282k109kHow it compares
Use this skill for Vercel Web Interface Guidelines compliance with file:line output rather than general accessibility audits or visual design reviews.
FAQ
Where does Web Design Guidelines fetch rules from?
Web Design Guidelines fetches the latest rules from https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md using WebFetch before each review, ensuring checks reflect current Vercel Web Interface Guidelines rather than stale cached rules.
What output format does Web Design Guidelines produce?
Web Design Guidelines outputs findings in a terse file:line format after checking specified frontend files against all fetched guideline rules. Developers receive precise locations for each interface compliance violation.
Is Web Design Guidelines safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.