mcpField
W
web-design-guidelines

web-design-guidelines

github.com/nexu-ioDesign & UI104.6k4.0k installsUpdated today
Repository

About web-design-guidelines

web-design-guidelines is a skill for reviewing files against Web Interface Guidelines. It uses a pinned local reference by default for reproducible checks, with an optional upstream update comparison, and reports findings in file-and-line format.

Key features

  1. 01Pinned guideline snapshot
  2. 02Optional upstream update check
  3. 03Review specified files or patterns
  4. 04Concise file-and-line findings

Use cases

  1. 01Auditing interface files against guidelines
  2. 02Checking whether upstream rules have changed

Install

Copy the command and run it in a terminal.

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

After installing, type/web-design-guidelinesin Claude Code to confirm it loaded.

Bundled filesreferences/guidelines.mdLICENSE

Details

From the project README

Web Interface Guidelines

Review files for compliance with Web Interface Guidelines.

How It Works

  1. Load the pinned guidelines from 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 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 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.

Comments

Markdown supported