AI Agent Hub
Back to skills
🎨

Web Interface Design Guidelines

Design & Media Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @org-02qudk26/web-design-guidelines into your AI assistant according to https://skillhub.cn/install/skillhub.md.

About this skill

Problem

Web UI issues are often not a single CSS rule or component; they include accessibility, interaction feedback, layout consistency, naming, and state presentation. Manual review can miss these details, and different projects may apply different interface standards, especially before code review.

How It Works

  • Fetch rules: Before each review, use WebFetch to retrieve the latest Web Interface Guidelines, avoiding stale rules.
  • Read targets: Read files or patterns supplied by the user; if none are specified, ask which files to review.
  • Compare item by item: Check file contents against all fetched rules and organize findings using the guideline-specified format.
  • Report tersely: List issues in file:line form so they can be located quickly.

Boundaries

This skill is for compliance review: it reports findings rather than generating designs, rewriting pages, or auto-fixing code. The exact rule set, scope, and output format depend on the fetched guidelines; unavailable sources or unclear file targets affect the result.

Use Cases

  • Before UI code review, read specified component files and check them against the latest interface guidelines.
  • After receiving interaction feedback, inspect a few files and locate rule violations as `file:line` findings.
  • When aligning on web standards, check specified files against the fetched guidelines before discussion.
  • Without clear file targets, confirm the review scope, then read files and output the findings.

Best For

  • Frontend engineers implementing web components who want guideline checks before review
  • Design engineering leads who need UI issues localized to `file:line`
  • Frontend engineers maintaining accessibility and interaction details who need file-level checklists
  • Code reviewers participating in web PRs who want guideline-specific findings