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 - Healthcare Audit Layer: Perform a secondary pass for HIPAA/ADA compliance including:
- Patient privacy verification (PHI check).
- Emergency contact accessibility (Direct tap-to-call).
- Doctor credentials & license number prominence.
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
- Enforce Healthcare Design Standards:
- Primary Blue (#2d54ff) contrast check.
- Trust Gold (#d4a574) legibility on Navy.
- Mobile tap targets must be 48x48px minimum for elderly patient ease of use.
If no files specified, ask the user which files to review.
Related Skills
| Skill | When to Use |
|---|---|
| frontend-design | Before coding - Learn design principles (color, typography, UX psychology) |
| web-design-guidelines (this) | After coding - Audit for accessibility, performance, and best practices |
Design Workflow
1. DESIGN → Read frontend-design principles
2. CODE → Implement the design
3. AUDIT → Run web-design-guidelines review ← YOU ARE HERE
4. FIX → Address findings from audit