Source profileQuality 68/100

nexu-io/open-design/skills/web-design-guidelines/SKILL.md

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.

Source repository stars: 91,167
Declared platforms: 0
Static risk flags: 1
Last source update: 2026-08-25
Source checked: 2026-08-25

Decision Compatibility Install Workflow Permissions Evidence Source FAQ

Decision brief

What it does: where it fits

Review files for compliance with Web Interface Guidelines.

Best for

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

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

Safe inspection promptEditorial

Inspect the Agent Skill "web-design-guidelines" from https://github.com/nexu-io/open-design/blob/edfa6b5f447e95cb120eae030f03baba00dc34de/skills/web-design-guidelines/SKILL.md at commit edfa6b5f447e95cb120eae030f03baba00dc34de. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
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 t…
Load references/guidelines.md as the default sourceOptionally fetch the upstream URL to check for updatesRead the specified files
02
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 (…
Load the pinned guidelines from references/guidelines.md — this is the default, reproducible execution pathOptionally, fetch the latest guidelines from the upstream URL below and diff against the pinned snapshot to see if anything has changedRead the specified files (or prompt user for files/pattern)
03
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.
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 env…Upstream (live): For users who want the very latest rules, the live source is available at:Fetching the live version is optional — the pinned snapshot is always the baseline.

Permission review

Static risk signals and limitations

Network access

medium · line 21

The documentation includes network, browsing, or remote request actions.

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

Network access

medium · line 30

The documentation includes network, browsing, or remote request actions.

Optionally fetch the upstream URL to check for updates

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	68/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	91,167	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: nexu-io/open-design
Skill path: skills/web-design-guidelines/SKILL.md
Commit: edfa6b5f447e95cb120eae030f03baba00dc34de
License: Apache-2.0
Collected: 2026-08-25
Default branch: main

View the original SKILL.md

Web Interface Guidelines

Review files for compliance with Web Interface Guidelines.

How It Works

Load the pinned guidelines from references/guidelines.md — this is the default, reproducible execution path
Optionally, fetch the latest guidelines from the upstream URL below and diff against the pinned snapshot to see if anything has changed
Read the specified files (or prompt user for files/pattern)
Check against all rules in the guidelines
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:

Load references/guidelines.md as the default source
Optionally fetch the upstream URL to check for updates
Read the specified files
Apply all rules from the guidelines
Output findings using the format specified in the guidelines

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

Frequently asked questions

What to verify before installation and use

What does the web-design-guidelines source document cover?

Review files for compliance with Web Interface Guidelines.

How do I install web-design-guidelines?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "skills/web-design-guidelines". Inspect the command and pinned source before running it.

Which permission-related actions were detected?

Static rules flagged network in the source; the page lists the matching lines and excerpts.

Alternatives

Compare before choosing

Computed 10045,511

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

Computed 100147

oaustegard/claude-skills

featuring

Generate hierarchical _FEATURES.md files that describe what a codebase DOES from a user/consumer perspective, anchored to source symbols via tree-sitting. Supports large complex codebases through feature-driven decomposition into sub-feature files. Uses a multi-pass synthesis: orientation → detail → overview rewrite. Use when someone says "what does this do", "document features", "feature inventory", "_FEATURES.md", or needs to understand a codebase's purpose before modifying it. Complements tre

Computed 1008

narrative-io/narrative-skills-marketplace

design-analysis

Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "

Computed 1007

event4u-app/agent-config

existing-ui-audit

Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.