epicenterhq/web-design-guidelines
.agents/skills/web-design-guidelines/SKILL.md
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".
$ install --global
skillsauthnpx skillsauth add epicenterhq/epicenter web-design-guidelinesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 12:26 PM4.5s1 file scanned
SKILL.md
- 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".
- author:
- vercel
- version:
- 1.0.0
- argument-hint:
- <file-or-pattern>
Web Interface Guidelines
Review files for compliance with Web Interface Guidelines.
When to Apply This Skill
Use this pattern when you need to:
- Audit UI code against Web Interface Guidelines.
- Review a site for accessibility, UX, or design best-practice compliance.
- Return terse
file:linefindings from a guidelines-driven review. - Re-check interfaces using the latest upstream guideline rules before reporting.
How It Works
- Fetch the latest guidelines from the source URL below
- Read the specified files (or prompt user for files/pattern)
- Check against all rules in the fetched guidelines
- Output findings in the terse
file:lineformat
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:
- Fetch guidelines from the source URL above
- Read the specified files
- Apply all rules from the fetched guidelines
- Output findings using the format specified in the guidelines
If no files specified, ask the user which files to review.
Related Skills
epicenterhq/yjs
documentation
VerifiedTrustedCommunity
Yjs CRDT patterns, shared types (Y.Map, Y.Array, Y.Text), conflict resolution, and document storage. Use when the user mentions Yjs, Y.Doc, CRDTs, collaborative editing, or when handling shared types, implementing real-time sync, or optimizing document storage.
4,428SKILL.mdUpdated Apr 17, 2026
epicenterhq/writing-voice
tools
VerifiedTrustedCommunity
Voice and tone rules for all written content—prose, UI text, tooltips, error messages. Use when the user says "fix the tone", "rewrite this", "sounds like AI", "sounds corporate", or when writing any user-facing text, landing pages, product copy, or open-source documentation.
4,428SKILL.mdUpdated Apr 17, 2026
epicenterhq/workspace-api
tools
VerifiedTrustedCommunity
Workspace API patterns for defineTable, defineKv, versioning, migrations, data access (CRUD + observation), withActions, and extension ordering. Use when the user mentions workspace, defineTable, defineKv, createWorkspace, withActions, withExtension, defineQuery, defineMutation, connectWorkspace, or when defining schemas, reading/writing table data, observing changes, writing migrations, chaining extensions, or attaching actions to a workspace client.
4,428SKILL.mdUpdated Apr 17, 2026
epicenterhq/workflow
documentation
VerifiedTrustedCommunity
Standard workflow for implementing features with specs and planning documents. Use when the user says "start a new feature", "how should I plan this", "what's the process", or when starting implementation, planning work, or working on any non-trivial task.
4,428SKILL.mdUpdated Apr 17, 2026