Skills ZICQ category：Agent Workflows web-design-guidelines

Web Design Guidelines

Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.

Official URL：GitHub

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.

When to use it

The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Web Interface Guidelines; How It Works; Guidelines Source; Usage.

File analysis

File analysis: besides SKILL.md, the body references references/guidelines.md. Those resources load on demand.

Web Interface GuidelinesHow It WorksGuidelines SourceUsage

Source category：GitHub skill

Sources & links

Market sources：GitHub

OSS Skill ranking

SKILL.md & Agent activation

Official spec ↗

name: web-design-guidelines
description: Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.

DiscoverThe client exposes names and descriptions to the agent.
ActivateYour request or the task context selects the skill and loads its instructions.
Load resourcesReferenced scripts, documentation and assets are used when needed.

Files referenced by the instructions · 1

references/guidelines.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "web-design-guidelines" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-3150c5ae17d5b6e5-Web-Design-Guidelines.html
Save it as .cursor/skills/web-design-guidelines/SKILL.md or .claude/skills/web-design-guidelines/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/nexu-io/open-design/tree/HEAD/skills/web-design-guidelines instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/nexu-io/open-design/tree/HEAD/skills/web-design-guidelines' --list

npx skills add 'https://github.com/nexu-io/open-design/tree/HEAD/skills/web-design-guidelines' --skill 'web-design-guidelines'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

SKILL.md source Copy freely; the source file is unchanged

# Web Interface Guidelines

Review files for compliance with Web Interface Guidelines.

## How It Works

1. Load the pinned guidelines from [`references/guidelines.md`](references/guidelines.md) — this is the default, reproducible execution path
2. Optionally, fetch the latest guidelines from the upstream URL below and diff against the pinned snapshot to see if anything has changed
3. Read the specified files (or prompt user for files/pattern)
4. Check against all rules in the guidelines
5. Output findings in the terse `file:line` format

## Guidelines Source

**Default (pinned):** The vendored copy at [`references/guidelines.md`](references/guidelines.md) is the default execution path. It is a pinned snapshot of the upstream guidelines and guarantees the skill produces reproducible results in any runtime environment.

**Upstream (live):** For users who want the very latest rules, the live source is available at:

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

Fetching the live version is optional — the pinned snapshot is always the baseline.

## Usage

When a user provides a file or pattern argument:
1. Load [`references/guidelines.md`](references/guidelines.md) as the default source
2. Optionally fetch the upstream URL to check for updates
3. Read the specified files
4. Apply all rules from the guidelines
5. Output findings using the format specified in the guidelines

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

Readable layout

--- name: web-design-guidelines description: | Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI. triggers: - "web design guidelines" - "vercel design" - "product ui standards" - "design checklist" - "review my UI" - "check accessibility" - "audit design" - "review UX" - "设计审查" metadata: author: vercel version: "1.0.0" argument-hint: od: mode: design-system surface: web platform: desktop category: design-systems upstream: "https://github.com/vercel-labs/web-interface-guidelines" source-commit: 4e799d45c17aec1498c269287a83b9dba22b966b preview: type: markdown example_prompt: | Review my UI code against the Vercel Web Interface Guidelines — check layout, typography, color, motion, and accessibility compliance. --- # Web Interface Guidelines Review files for compliance with Web Interface Guidelines. ## How It Works 1. Load the pinned guidelines from [`references/guidelines.md`](references/guidelines.md) — this is the default, reproducible execution path 2. Optionally, fetch the latest guidelines from the upstream URL below and diff against the pinned snapshot to see if anything has changed 3. Read the specified files (or prompt user for files/pattern) 4. Check against all rules in the guidelines 5. Output findings in the terse `file:line` format ## Guidelines Source **Default (pinned):** The vendored copy at [`references/guidelines.md`](references/guidelines.md) is the default execution path. It is a pinned snapshot of the upstream guidelines and guarantees the skill produces reproducible results in any runtime environment. **Upstream (live):** For users who want the very latest rules, the live source is available at: ``` https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md ``` Fetching the live version is optional — the pinned snapshot is always the baseline. ## Usage When a user provides a file or pattern argument: 1. Load [`references/guidelines.md`](references/guidelines.md) as the default source 2. Optionally fetch the upstream URL to check for updates 3. Read the specified files 4. Apply all rules from the guidelines 5. Output findings using the format specified in the guidelines If no files specified, ask the user which files to review.

Related skills

Agent Workflows

Web Design Guidelines

What this skill does

What it does

When to use it

How agents load it

File analysis

SKILL.md & Agent activation

Install this skill

Related skills

Skill Creator

Clawdhub

Agent Team Orchestration

Superpowers