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
82,073
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and 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

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability 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/89d6d4ef21baf80f871595abdf6f7de6e941dd44/skills/web-design-guidelines/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. 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

    1. 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
    2. 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)
    3. 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 20

    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 29

    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
    SignalValueEvidence typeMeaning
    Quality score68/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars82,073SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated 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
    89d6d4ef21baf80f871595abdf6f7de6e941dd44
    License
    Apache-2.0
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    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.

    Alternatives

    Compare before choosing

    Computed 5929,549

    vercel-labs/agent-skills

    web-design-guidelines

    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".

    2026-07-240 platforms
    Computed 10042,015

    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

    2026-07-270 platforms
    Computed 1007

    event4u-app/agent-config

    design-intelligence

    Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

    2026-07-280 platforms
    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.

    2026-07-280 platforms