design-qa
Skill0 starsChanged 37 days agoMITView on GitHub
Render-and-critique loop for landing pages - screenshot the built page in headless Chrome at mobile and desktop widths, visually critique the screenshots against the landing-page-visual-standards checklist, fix, and re-render until it passes. Use in Claude Code whenever a landing page or funnel page HTML file has been built or edited, before presenting it to the user. Trigger on "QA this page", "check the design", "does this look right", or automatically as the final step of any landing page build. Requires a local environment that can run Node + Playwright (Claude Code, not claude.ai chat).
- Installs packages
11 other projects use a version of this.
Adopted by
Most recently taken up by
- plugin87/ux-ui-agent-skillstheir own version, first seen Nov 10, 2026
- robritacca-dotcom/rift-dstheir own version, first seen Nov 1, 2026
- robritacca-dotcom/design-systemtheir own version, first seen Oct 28, 2026
- adityareddy-dev/deskstudiotheir own version, first seen Oct 25, 2026
- yair-zehavi/claude-code-skillstheir own version, first seen Oct 17, 2026
- openai/pluginstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use accessibility-audit and ship.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GitHubSkillaccessibility-audit
Audits actual components and routes against applicable WCAG 2.2 A/AA criteria using consumer-owned design-system evidence and repository tools. Use when asked for an accessibility audit, a11y check, keyboard or focus review, contrast check, or screen-reader verification.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- openai/plugins★ 7.8ksame name
- plugin87/ux-ui-agent-skills★ 3.2ksame name
- adityareddy-dev/deskstudio★ 43same name
- calven-ai/marketing-as-code★ 10same name
- robritacca-dotcom/rift-ds★ 9same name
- tstapler/dotfiles★ 8same name
- p-slatts/design-qa★ 4same name
- NiavisDimitris/skills★ 3same name
- humbleteam/design-qa★ 1same name
- robritacca-dotcom/design-system★ 1same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- agency-positioning-expertSkill
- case-study-writerSkill
- chief-marketing-officerSkill
- clay-enrichment-architectSkill
- cold-email-outreachSkill
- content-market-intelligenceSkill
- email-marketingSkill
- ghl-snapshot-builderSkill
- go-high-level-expertSkill
- google-ads-expertSkill
- google-tag-manager-expertSkill
- icp-filter-architectSkill
- instagram-content-creatorSkill
- landing-page-designerSkill
- landing-page-visual-standardsSkill
- linkedin-outreach-architectSkill
- linkedin-post-writerSkill
- looker-studio-expertSkill
- meta-ads-expertSkill
- n8n-workflow-expertSkill
- outreach-message-criticSkill
- seo-client-outreachSkill
- youtube-gap-finderSkill
- youtube-video-ideationSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Fix everything found. Re-render. Re-critique: Do not present the page to the user until a pass produces zero findings, or remaining …
- Distinctive: line 40
Never skip the mobile fold screenshot - 70%+ of paid traffic is mobile and the fold decides the bounce.
- Distinctive: line 42
If Playwright is unavailable, say so and fall back to line-by-line CSS review - but flag that visual QA didn't run.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design QA - Render, Look, Fix, Repeat
Code review is not design review. This skill forces the loop a human designer runs by default: look at the rendered page, not the source.
Setup (once per machine)
npm init -y && npm install playwright
npx playwright install chromiumThe loop (minimum 2 passes, typical 3)
- Render the page at both breakpoints:
Producesnode scripts/screenshot.js path/to/page.htmlqa/page-390.png(mobile, full page) andqa/page-1440.png(desktop, full page) plusqa/page-390-fold.png(mobile above-the-fold only). - Read all three screenshots and critique them against
landing-page-visual-standards/CHECKLIST.md, plus these render-only checks that source code can't reveal:- Above-the-fold (mobile): is the CTA fully visible? Is the headline uncomfortably wrapped (widows, 1-word lines)?
- Spacing rhythm: do section gaps look even? Any section cramped against another?
- Contrast in practice: is body text comfortably readable on its actual background?
- Overflow: any horizontal scrollbar, clipped text, or element bleeding off-canvas at 390px?
- The signature element: does it actually read as the hero moment, or does it get lost?
- Font loading: did the display face render, or is it showing a fallback?
- Squint test: blur your reading of the desktop shot - does the eye land on the CTA first?
- Fix everything found. Re-render. Re-critique. Do not present the page to the user until a pass produces zero findings, or remaining findings are explicitly listed as accepted trade-offs.
- Present the final screenshots alongside the file so the user sees what you saw.
Rules
- Never skip the mobile fold screenshot - 70%+ of paid traffic is mobile and the fold decides the bounce.
- Fix in code, never by cropping the screenshot story.
- If Playwright is unavailable, say so and fall back to line-by-line CSS review - but flag that visual QA didn't run.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

