web-design-guidelines
Skill0 starsChanged 10 months agoMITView on GitHub
Review UI code for Web Interface Guidelines compliance. Use when reviewing UI code, checking accessibility standards, auditing design consistency, or validating sites against best practices.
176 other projects use a version of this, 162 of them edited.
Adopted by
Most recently taken up by
- yuiseki/GeoAI-master-skillsedited, first seen Nov 8, 2026
- open-slide/open-slideedited, first seen Nov 8, 2026
- arch3rPro/Skills-Spaceedited, first seen Nov 8, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
- Contentrain/studioedited, first seen Nov 8, 2026
- eea/eea.agent.skillsedited, first seen Nov 8, 2026
Used with
Projects with it also use canvas-procedural-animation, intelligent-routing and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LinHao-citySkillcanvas-procedural-animation
Use p5.js/canvas for local procedural character effects: particles, weather, squash/stretch, walk cycles, and environmental motion.
Also in 5 projects that use this
SKB3002Skillintelligent-routing
Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.
Also in 5 projects that use this
VercelSkillvercel-optimize
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
Also in 15 projects that use this
thongdn-itSkillnuqs
nuqs (type-safe URL query state) best practices for Next.js applications. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, or Next.js routing with state.
Also in 4 projects that use this
- LinHao-citySkill
pose-library-design
Design reusable 2D character pose libraries, action cycles, and expression states for data-driven animation.
Also in 4 projects that use this
stophobiaSkillsurprise-me
Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for "something interesting".
Also in 4 projects that use this
- +2 more from LinHao-city
Other versions176 projects use a version of this.
Word for word · 0
None found.
Edited · 162
- bytedance/deer-flow★ 85k81% same
- calesthio/OpenMontage★ 78k81% same
- OpenMontageInc/OpenMontage★ 78k81% same
- multica-ai/multica★ 55k81% same
- moeru-ai/airi★ 51k81% same
- vercel-labs/agent-skills★ 33k81% same
- awesome-dsh-plugin/awesome-dsh-plugin★ 24k81% same
- open-metadata/OpenMetadata★ 16k81% same
- trycompai/crm★ 12k81% same
- mengxi-ream/read-frog★ 10k81% same
152 more not listed
Wrote their own version · 14
- OpenBMB/PilotDeck★ 5ksame name
- CloudAI-X/claude-workflow★ 1.4ksame name
- CloudAI-X/claude-workflow-v2★ 1.4ksame name
- ehmo/platform-design-skills★ 603same name
- baekenough/oh-my-customcode★ 42same name
- kumaran-is/claude-code-onboarding★ 35same name
- sabahattink/antigravity-fullstack-hq★ 30same name
- afonsoft/skills★ 14same name
- excatt/superclaude-plusplus★ 14same name
- jhy0285/monofield★ 6same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- architectSkill
- brainstormingSkill
- concise-planningSkill
- context-engineerSkill
- data-deprecation-analysisSkill
- data-modelerSkill
- data-pipeline-engineerSkill
- data-quality-frameworksSkill
- dbt-transformation-patternsSkill
- github-workflow-automationSkill
- guardianSkill
- implementerSkill
- json-to-pydanticSkill
- llm-app-patternsSkill
- navigatorSkill
- ops-managerSkill
- orchestratorSkill
- principal-data-engineerSkill
- product-manager-toolkitSkill
- proj-memorySkill
- prompt-librarySkill
- qa-testerSkill
- researcherSkill
- senior-data-engineerSkill
- software-architectureSkill
- spark-optimizationSkill
- sql-optimization-patternsSkill
- state-managerSkill
- subagent-driven-developmentSkill
- thinkerSkill
- top-web-vulnerabilitiesSkill
- verification-before-completionSkill
- workflow-managerSkill
The file
We split this skill into the rules it gives an agent
9 rules. 6 are common, 3 are distinctive, and 0 are very specific to this project.
6
Common
Most of the 173 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 20
Read the specified files (or prompt user for files/pattern)
- Common: line 21
Check against all rules in the fetched guidelines
- Common: line 32
Use WebFetch to retrieve the latest rules.
- Common: line 36
When a user provides a file or pattern argument:
- Common: line 39
Read the specified files
- Common: line 43
If no files specified, ask the user which files to review.
- Distinctive: line 49
Success Criteria: No critical accessibility failures and clear remediation steps for others
- Distinctive: line 54
Technical Constraints: Do not modify source files automatically.
- Distinctive: line 56
Governance Constraints: Use latest guidelines from the canonical source before each review
“Common” is measured: kept by at least 6 in 10 of the 173 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.mdUse 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.
Outputs & Deliverables
- Primary Output: Accessibility and design review findings in
file:lineformat and a short remediation list - Secondary Output: Suggested code snippets or CSS fixes for small violations
- Success Criteria: No critical accessibility failures and clear remediation steps for others
- Quality Gate:
implementerreview for fixes prior to merge
Constraints
- Technical Constraints: Do not modify source files automatically; produce recommended fixes only
- Scope Constraints: Focus on UI guidelines and accessibility; visual design approvals are separate
- Governance Constraints: Use latest guidelines from the canonical source before each review
Common Pitfalls
- Stale Guidelines: Using local cached guidelines instead of fetching fresh ones. Always fetch from the canonical source before each review.
- Skipping Accessibility: Checking only visual design, not keyboard navigation or screen reader support. Accessibility is mandatory, not optional.
- Ignoring Contrast Ratios: Visual text looks fine but fails WCAG contrast requirements. Always validate color contrasts programmatically.
- Missing Responsive Testing: UI looks good on desktop but breaks on mobile. Test at multiple breakpoints.
- Not Suggesting Fixes: Reporting problems without showing how to fix them. Always provide remediation code snippets.
- Vague Findings: "Design looks off" instead of specific violations. Reference exact lines and rules.
Integration Points
| Phase | Input From | Output To | Context |
| Review Request | UI code files | Guidelines fetch | Retrieve canonical guidelines from source |
| Analysis | Code patterns and styles | Findings report | Identify violations against guidelines |
| Remediation | Violations found | implementer | Provide code examples for fixes |
| Merge Gate | UI changes complete | QA approval | No critical accessibility issues before merge |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.