.agents/skills/web-design-guidelines/SKILL.md
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".
npx skillsauth add teamzisty/deni-ai web-design-guidelinesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Review files for compliance with Web Interface Guidelines.
file:line formatFetch 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.
When a user provides a file or pattern argument:
If no files specified, ask the user which files to review.
development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
development
Run TypeScript type checking for this repository. Use when the user asks to typecheck, validate TypeScript changes, or inspect compiler errors. Execute `bun run typecheck`, summarize any errors, and suggest targeted fixes when type errors remain.
development
Sync `messages/en.json` and `messages/ja.json` for this repository. Use when the user asks to update translations, fill missing Japanese strings, or remove stale i18n keys. Run `bun run build` before reading translations, then add missing Japanese entries, fill empty values, remove stale keys, preserve key order from `en.json`, and keep placeholders, ICU syntax, and brand names unchanged.
development
Run repository linting and formatting with auto-fix. Use when the user asks to fix lint issues, run formatting, or clean up code style. Execute `bun run lint:fix`, then `bun run format`, and report any remaining issues that need manual attention.