web-design-guidelines

Apply the upstream Web Interface Guidelines workflow to review UI code for accessibility, design quality, and consistency.

108|27|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/diegosouzapw/omni-skills --skill web-design-guidelines-diegosouzapw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-design-guidelines
Source: https://github.com/diegosouzapw/omni-skills/tree/main/skills/web-design-guidelines
Command: npx skills add https://github.com/diegosouzapw/omni-skills --skill web-design-guidelines-diegosouzapw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The Web Design Guidelines skill packages upstream design-review guidance into a native Omni Skills intake, preserving provenance and source context, making audits auditable while keeping task-relevant workflow visible.

Core Features & Use Cases

  • Upstream workflow packaging: preserves the original guidelines and makes them auditable within Omni Skills.
  • Provenance and context: keeps source links, commit, and path visible in notes and handoffs.
  • Lightweight supporting assets: includes a checklist, rubric, playbook, and router guidance to guide execution.

Quick Start

Load the upstream workflow and run the packaged intake to review a UI against the guidelines.

Frequently Asked Questions about web-design-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit web UI code against official design guidelines?

Audit web UI code by loading the upstream Web Interface Guidelines workflow to review accessibility, design quality, and consistency. The packaged skill applies a built-in checklist and rubric to evaluate UI code while preserving source provenance.

What is provenance visibility in a UI audit workflow?

Provenance visibility in a UI audit workflow keeps source links, commit data, and file paths visible in notes and handoffs. This ensures design reviews remain auditable and traceable back to their original upstream guidelines.

How do I review UI code for accessibility and consistency in a PR?

Review UI code for accessibility and consistency in PRs by applying the packaged upstream workflow and intake checklist. The skill enforces design quality standards and generates structured review notes suitable for pull request evaluations.

Can I run a UX audit without loading all upstream design files?

You can run a UX audit by loading only the necessary upstream files. The skill includes router guidance that directs the workflow to fetch relevant design assets, keeping the audit lightweight while maintaining guideline compliance.

Does this design review skill preserve source context for handoffs?

The design review skill preserves source context by maintaining provenance visibility across notes and handoffs. Original guidelines, commit references, and path data stay attached to the review output for full auditability.

What is the best way to evaluate site UI against upstream design standards?

Evaluate site UI against upstream design standards by running the packaged intake workflow with its built-in rubric and playbook. This approach enforces provenance visibility and ensures site evaluations align with official interface guidelines.