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".
pinned to #be63716updated 3 months ago
Ask your AI client: “install skills/web-design-guidelines”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/web-design-guidelinesmetahub onboarded this repo on the author's behalf.
If you own github.com/bytedance/deer-flow on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
76,729
Last commit
3 months ago
Latest release
published
- #agent
- #agentic
- #agentic-framework
- #agentic-workflow
- #ai
- #ai-agents
- #deep-research
- #harness
- #langchain
- #langgraph
- #langmanus
- #llm
- #multi-agent
- #nodejs
- #podcast
- #python
- #superagent
- #typescript
About this skill
Pulled from SKILL.md at publish time.
Review files for compliance with Web Interface Guidelines.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.be63716· 3 months ago
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Kind-specific
2 passed2 warningsSkill: body content presentwarn
Body is short (136 words · 914 chars) — Claude has little to go on
Add concrete usage steps, example invocations, and any reference links. (≥3 code blocks lifts a short body to pass.)
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: SKILL.md present
found at skills/public/web-design-guidelines/SKILL.md · frontmatter source: SKILL.md
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrentbe63716warn3 months ago
Contents
Web Interface Guidelines
Review files for compliance with Web Interface Guidelines.
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.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/web-design-guidelines