web-design-guidelines

"Use when: review UI code, audit accessibility, check UX, or compare a site against current Web Interface Guidelines."

Repository: kimtth/agent-skill-100-lines-or-less
Last source activity: May 22, 2026 at 12:33
Detected SKILL.md language: English
Stars: 2
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/kimtth/agent-skill-100-lines-or-less --skill web-design-guidelines

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

name	web-design-guidelines
description	Use when: review UI code, audit accessibility, check UX, or compare a site against current Web Interface Guidelines.
metadata	null
author	vercel
version	1.0.0
argument-hint	<file-or-pattern>

Goal: review real UI files against the latest web interface rules.

Workflow:

Fetch fresh guidelines from: https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
Read the user-provided file or glob. If none is provided, ask for scope.
Check layout, accessibility, copy, responsive behavior, and interaction polish.
Report findings in the terse format required by the fetched guidelines.

Use for:

"review my UI", "audit this design", "check accessibility"
landing pages, apps, dashboards, forms, and component previews
visual issues that need file-backed evidence, not taste alone

Output:

findings first: file:line | rule | issue | fix
note only the highest-signal passes when there are no findings
mention when guidelines could not be fetched

Rules:

tie each critique to a visible user outcome
prefer concrete file edits over design vocabulary
remove weak UI before adding ornament
fetch the guideline source before each review
do not invent rules that are not in the fetched document
ask for target files when scope is missing

web-design-guidelines

Source facts

Install options

Review the source files

More from this repository

More from this repository