Skip to content
Back to skills

Web Design Guidelines

ASecurity

Review 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", and for the guidelines re-run in every frontend visual demo.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 11, 2026
ai-agentsgitfrontend

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned November 11, 2026

npx -y skills add abhijeetgupta23/ai-agent-to-learn-faster-and-better --skill web-design-guidelines --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Web Design Guidelines?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Web Design Guidelines
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/abhijeetgupta23-web-design-guidelines/badge)](https://www.skillsdirectory.com/skills/abhijeetgupta23-web-design-guidelines)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: web-design-guidelines
description: Review 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", and for the guidelines re-run in every frontend visual demo.
metadata:
  author: vercel
  version: "1.0.0"
  argument-hint: <file-or-pattern>
---

<!-- Adapted from vercel-labs/agent-skills (MIT, commit 6ec2693). Change: the rules are vendored in
     guidelines.md (vercel-labs/web-interface-guidelines command.md, MIT, commit 434b7f9) instead of
     fetched from GitHub on every run, so reviews are offline, pinned and reviewed. -->

# Web Interface Guidelines

Review files for compliance with Web Interface Guidelines.

## How It Works

1. Read the rules in `guidelines.md` next to this file (do not fetch them from the web).
2. Read the specified files (or ask which files to review).
3. Check against all rules in `guidelines.md`.
4. Output findings in the terse `file:line` format it describes.

## Usage

When a file or pattern is given:
1. Read `guidelines.md`
2. Read the specified files
3. Apply all rules
4. Output findings using the format specified in the guidelines

If no files are specified, ask which files to review. To refresh the rules, update `guidelines.md` in a PR.

Project rules win over the guidelines: in this repo there are no CDN or third-party asset domains to preconnect to (fonts are self-hosted), and text contrast must be at least 4.5:1.

Files in this skill

  • LICENSE1 KB
  • SKILL.md1.5 KB
  • guidelines.md7.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.