Agent Skills
› tech-leads-club/agent-skills
› web-design-guidelines
web-design-guidelines
GitHub审查前端UI代码是否符合Web界面指南，涵盖无障碍、交互、样式等规范。适用于用户要求检查UI、可访问性或设计合规性的场景。
Trigger Scenarios
review my UI
check accessibility
audit design
review UX
check my site against best practices
Install
npx skills add tech-leads-club/agent-skills --skill web-design-guidelines -g -y
SKILL.md
Frontmatter
{
"name": "web-design-guidelines",
"metadata": {
"author": "vercel",
"version": "1.0.0",
"argument-hint": "<file-or-pattern>"
},
"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\". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit)."
}
Web Interface Guidelines
Review files for compliance with Web Interface Guidelines.
How It Works
- Read the guidelines from
#[[file:references/guideline.md]] - Read the specified files (or prompt user for files/pattern)
- Check against all rules in the guidelines
- Output findings in the terse
file:lineformat
Guidelines Reference
All rules and output format instructions are in:
#[[file:references/guideline.md]]
The guidelines cover:
- Accessibility (ARIA, semantic HTML, keyboard navigation)
- Focus states and keyboard interaction
- Forms (autocomplete, validation, labels)
- Animation (reduced motion, performance)
- Typography (proper characters, number formatting)
- Content handling (overflow, empty states)
- Images (dimensions, lazy loading)
- Performance (virtualization, DOM reads)
- Navigation & state (URL sync, deep linking)
- Touch & interaction (tap delays, safe areas)
- Dark mode & theming
- Locale & i18n
- Hydration safety
- Common anti-patterns to flag
Usage
When a user provides a file or pattern argument:
- Read the guidelines from
references/guideline.md - Read the specified files
- Apply all rules from the guidelines
- Output findings using the format specified in the guidelines
If no files specified, ask the user which files to review.
Output Format
Follow the format in the guidelines:
- Group findings by file
- Use
file:lineformat (VS Code clickable) - Terse, high signal-to-noise
- State issue + location
- Skip explanation unless fix is non-obvious
Version History
- 39e57ed Current 2026-07-25 05:42
