Agent skill · practicalswan
web-design-guidelines
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\".
What it needs
About 2k tokens when loaded.
What this skill does
Web Interface Guidelines Review files for compliance with Web Interface Guidelines. How It Works 1. Fetch the latest guidelines from the source URL below 2. Read the specified files (or prompt user for files/pattern) 3. Check against all rules in the fetched guidelines 4. Output findings in the terse file:line format Guidelines Source Fetch fresh guidelines before each review: 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: 1. Fetch guidelines from the source URL above 2. Read the specified files 3. Apply all rules from the fetched guidelines 4. Output findings using the format specified in the guidelines If no files specified, ask the user which files to review. <!-- MCP:START --> <!-- PORTABILITY:START --> Cross-Client Portability This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex. GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the workflow in project instructions when folder discovery is unavailable. Claude Code: keep the folder in a local skills directory or a compatible plugin source. Codex: install or sync the folder into $CODEXHOME/skills/web-design-guidelines and restart Codex after major changes. <!-- PORTABILITY:END --> MCP Availability And Fallback Preferred MCP Server: None required Fallback prompt: "Use the Web Interface Guidelines skill without MCP. Rely on its local instructions, bundled resources, standard shell or editor tools, and direct verification. Show the evidence used before concluding." Do not claim an MCP operation was used when the active host does not expose it. Treat local files, tests, rendered outputs, logs, or screenshots as the fallback evidence path. <!-- MCP:END --> Anti-Patterns Activating web-design-guidelines outside its documented task boundary. Skipping required source, prerequisite, safety, or approval checks. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills practicalswan/web-design-guidelines