web-design-guidelines

---
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".
metadata:
  author: vercel
  version: "1.0.0"
  argument-hint: <file-or-pattern>
---

# 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.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:
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.

## 한 줄

검사할 때마다 `https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md`에서 규칙을 새로 받아 온다 — 규칙이 스킬 안에 박혀 있지 않으니 따로 업데이트할 필요가 없다.

*EN: Rules are fetched fresh on every run, not baked in, so they never go out of date.*

## 언제 쓰는가

- "내 UI 검토해줘", "접근성 체크", "디자인 audit(감사)", "UX(사용자 경험) review"
- "best practices(모범 사례)에 맞는지 확인"

## 동작

1. 위 URL에서 최신 가이드라인 fetch(받아 오기)
2. 사용자가 지정한 파일/패턴 read(읽기) (없으면 물어봄)
3. 모든 룰 적용
4. 결과를 `file:line`(파일:줄 번호) 짧은 형식으로 출력 (수정 빠르게 할 수 있게)

## 함정

파일을 안 알려주면 그냥 멈춰서 묻는다. 자동으로 전체 repo를 스캔하지 않음.

## 원문 SKILL.md

````markdown
---
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".
metadata:
  author: vercel
  version: "1.0.0"
  argument-hint: <file-or-pattern>
---

# 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.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:
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.
````