Web Design Guidelines

Use this skill when the question is "how good is this interface overall, what is creating friction, and what should we fix first?"

This is the repo's broad interface audit / design-review anchor. It is not just a vendor-rule fetcher and it is not a replacement for specialized neighboring skills.

Read references/review-modes-and-categories.md before handling a broad page or flow review. Read references/handoff-boundaries.md when deciding whether the work belongs here, web-accessibility, responsive-design, ui-component-patterns, design-system, or react-best-practices. Read references/ui-audit-packet-template.md before writing a final review packet.

When to use this skill

• Review a landing page, dashboard, signup flow, settings page, or marketing site for broad interface quality
• Turn "review my UI" or "audit this UX" into a structured audit instead of scattered opinions
• Judge hierarchy, clarity, spacing, consistency, component-state quality, CTA emphasis, and task friction together
• Check whether a screen or flow is ready for implementation, release, or stakeholder review
• Compare a page against broad interface heuristics and practical implementation guidelines
• Convert mixed findings into one prioritized UI audit packet with explicit handoffs