t1k:web:ui:guidelines
| Field | Value |
|---|---|
| Module | ui |
| Version | 1.7.0 |
| Effort | low |
| Tools | — |
Keywords: accessibility, audit, best practices, guidelines, review, UX, web design
How to invoke
Section titled “How to invoke”/t1k:web:ui:guidelines[file-or-pattern]Web Interface Guidelines
Section titled “Web Interface Guidelines”Review files for compliance with Web Interface Guidelines.
How It Works
Section titled “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
Section titled “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.
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.
Gotchas
Section titled “Gotchas”- Guidelines without enforcement are aspirational — pair with CI lint (Stylelint, axe-core) or they drift in 30 days.
- Brand voice across components needs an audit cadence — tokens lock visuals; only humans lock voice.