ada-web-ui-design-review

Audit and redesign web app UI using real-browser evidence across viewport matrices.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-web-ui-design-review-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-web-ui-design-review
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-web-ui-design-review
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-web-ui-design-review-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires puppeteer-core, pillow, and includes scripts (resource) and references (resource) components.

What problem does it solve? Web UI reviews often rely on subjective opinions and guesswork, leading to inconsistent design changes, unfixed responsive defects, and accessibility regressions. This Skill enforces an evidence-based workflow: audit with a real browser, propose a design direction, get approval, then implement and verify. ## Core Features & Use Cases - Evidence-based audit: Captures screenshots across a 320–1440px viewport matrix, reads computed styles and rendered geometry, checks horizontal overflow in open and closed UI states, and computes WCAG contrast ratios. - Structured four-part review: Delivers current UI assessment, design direction with keep/weaken/delete lists, page structure proposal, and a prioritized improvement plan before any code changes. - Guided implementation and verification: Implements in priority order (tokens → layout → typography → components → responsive) and verifies each change with puppeteer assertions, build, and test gates. - Use Case: A user reports that section numbering is inconsistent across a portfolio site and the mobile menu overflows at 375px. The Skill audits the whole structural family, measures the open-menu bounding box, proposes fixes, and verifies rendered geometry after the change. ## Quick Start Ask the agent to review your web app's UI, for example: "Review my site's UI, find responsive and accessibility problems, and propose a redesign before changing any code."

Frequently Asked Questions about ada-web-ui-design-review

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

FAQPage Schema
How do I audit a website's UI with real browser evidence?

Run the app locally, capture screenshots across a 320/375/430/768/1024/1440 viewport matrix, and read computed styles and bounding boxes via page.evaluate. Check horizontal overflow in both closed and open UI states, and compute WCAG contrast ratios for every text color pair.

How to take screenshots of a Blazor WASM app in headless Chrome?

Plain chrome --headless --screenshot captures only the loader page because the WASM download is real network time. Use puppeteer-core with system Chrome and waitForFunction on a rendered selector like main h1 before screenshotting.

Why does horizontal overflow only appear when a menu is open?

Closed-state overflow checks miss overlays: a dropdown anchored to a right-edge hamburger can extend past the viewport only while open. Open every disclosure at each collapsed-nav width and measure its bounding rectangle, not just document scrollWidth.

Can I check WCAG color contrast without a design tool?

Yes, compute the contrast ratio programmatically from hex color pairs using the WCAG relative luminance formula. The included visual-evidence.py script reports the ratio and pass/fail verdict, for example gold #e6a817 on white is only 2.10:1 and fails.

When should design changes be approved before editing code?

Always for UI redesign requests: deliver the assessment, design direction, keep/weaken/delete lists, and prioritized plan first, then wait for explicit user approval. Gates prove behavior and build integrity, but the user's visual confirmation on the running site is the final gate.