Web Design Guidelines

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — None to install this skill — no account, no key, no payment; its folder is a single SKILL.md. Remote fetch at use time, disclosed up front: this skill holds no rules itself — before each review it fetches the latest guidelines with WebFetch from https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md (another public Vercel Labs repository), so using it requires network access at review time, and the fetched file supplies both the rules and the output-format instructions it follows. Install "Web Design Guidelines" for me. It is a one-file review skill: when I ask it to review my UI, check accessibility, audit my design or review my UX, it first fetches the latest Web Interface Guidelines from the source URL named in the SKILL.md, then reads the files I specify (or asks me which files to review), checks them against every rule in the fetched guidelines, and outputs its findings in the terse file:line format the guidelines specify. The folder contains nothing else: no rules, no script, no companion files — the rule set lives in the separate vercel-labs/web-interface-guidelines repository and is fetched fresh at each review. Repository: https://github.com/vercel-labs/agent-skills (the skill is the whole skills/web-design-guidelines/ folder at the pinned commit: SKILL.md only, 1 file in total) Pinned version: install the code at commit 063bee94c3f4df8453406c830b0a7df0f2860278 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/vercel-labs/agent-skills into a temporary folder, check out commit 063bee94c3f4df8453406c830b0a7df0f2860278, and copy the skills/web-design-guidelines/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 f4647ca866a3accf763777f83e7682954f0187cd6bea7eea0399796652414e8f If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds exactly 1 file: a 1,231-byte SKILL.md (frontmatter name web-design-guidelines). There is no script, no rule file and no other code or content in it. - Nothing is sent anywhere during installation itself; the only download at install time is that single file from GitHub at the pinned commit, and none of my files are read during installation. - At use time the skill fetches its rule set fresh from raw.githubusercontent.com (the command.md of the vercel-labs/web-interface-guidelines repository) before each review and reads the files I name locally. That fetch is a download of public guidelines; the SKILL.md describes no sending of my files anywhere, and no personal information or credentials are read or sent. - Do not fetch the guidelines, do not review any file of mine, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for a UI review later. 3. When I say "yes, install", install it as a skill: copy the whole web-design-guidelines folder into the agent's skills directory, in a folder named exactly "web-design-guidelines", keeping its 1 file in its original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: web-design-guidelines), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that the skill contains no rules itself and fetches them fresh from GitHub at each review (network access needed at use time), and that using it is a separate step that only starts when I ask for a UI review). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.