responsive-audit
Skill0 starsChanged 7 months agoMITView on GitHub
Audit a component for responsive behaviour using dev-browser. Screenshots it at multiple breakpoints, reads the visual output, reads the source code, identifies responsive issues, and produces a concrete fix plan. Optionally compares against a reference URL. Requires dev-browser CLI. Use when asked to "make this responsive", "check responsive", "audit breakpoints", or "fix mobile layout".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- github/replicatheir own version, first seen Nov 1, 2026
- UXLana/design-skills-packtheir own version, first seen Oct 25, 2026
- Gaurav890/everything-agentic-engineeringtheir own version, first seen Sep 13, 2026
- hemantyadav79/Claude-Skillstheir own version, first seen Aug 17, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- github/replica★ 275same name
- UXLana/design-skills-pack★ 8same name
- Gaurav890/everything-agentic-engineering★ 1same name
- hemantyadav79/Claude-Skills★ 0same name
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 repository8 other files it gives its agents.
- autopilot-executeSkill
- close-planSkill
- deep-modules-auditSkill
- docs-auditSkill
- execute-phaseSkill
- lint-fixSkill
- living-design-systemSkill
- phased-planSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Use dev-browser --headless to capture the component at each project breakpoint.
- Very specific: line 62
Use the read tool on each saved screenshot PNG.
- Very specific: line 71
If a reference URL is provided (e.g.
- Distinctive: line 80
Read all component source files.
- Distinctive: line 122
Commit with a descriptive message noting the responsive changes:
“Common” is measured: kept by at least 6 in 10 of the 4 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
Responsive Audit
Visually audit a component's responsive behaviour by screenshotting it at standard breakpoints, then produce a fix plan or implement the fixes.
Prerequisites
dev-browserCLI installed and available on PATH- Dev server running (e.g.
localhost:3000,localhost:5173,localhost:4321, etc.) - Playwright browsers installed (
dev-browser installif needed)
Process
Step 1 — Locate the component
Identify:
- The preview URL — the page or embed URL that renders the component in isolation
- The source files — find all relevant component files (
.tsx,.vue,.svelte,.astro,.jsx, etc.) - The project's breakpoint system — look for breakpoint definitions in the codebase (e.g.
Breakpoints.tsx,tailwind.config.*,global.css@themeblock). Use these breakpoints, not arbitrary ones.
Step 2 — Screenshot at all breakpoints
Use dev-browser --headless to capture the component at each project breakpoint. At minimum capture these widths:
| Name | Width | Represents |
| mobile | 375px | Phone (portrait) |
| tablet | 768px | Tablet (portrait) |
| laptop | 1024px | Small laptop / tablet landscape |
| desktop | 1440px | Desktop |
Script pattern:
dev-browser --headless <<'EOF'
const page = await browser.getPage("responsive-audit");
await page.goto("<URL>", { waitUntil: "networkidle" });
const breakpoints = [
{ name: "mobile-375", width: 375, height: 800 },
{ name: "tablet-768", width: 768, height: 1024 },
{ name: "laptop-1024", width: 1024, height: 768 },
{ name: "desktop-1440", width: 1440, height: 900 },
];
for (const bp of breakpoints) {
await page.setViewportSize({ width: bp.width, height: bp.height });
await new Promise(r => setTimeout(r, 500));
const buf = await page.screenshot({ fullPage: true });
const path = await saveScreenshot(buf, `audit-${bp.name}.png`);
console.log(`${bp.name}: ${path}`);
}
EOFStep 3 — View and analyse screenshots
Use the read tool on each saved screenshot PNG. For each breakpoint, note:
- Is there horizontal overflow?
- Are elements overlapping or cramped?
- Is text readable?
- Are interactive elements (buttons, links) tap-target sized on mobile?
- Is the layout appropriate for the viewport width?
Step 4 — (Optional) Compare against reference
If a reference URL is provided (e.g. the production site), screenshot it at the same breakpoints and compare the layout patterns. Use domcontentloaded instead of networkidle if the site is slow:
await page.goto("<REFERENCE_URL>", { waitUntil: "domcontentloaded", timeout: 15000 });
await new Promise(r => setTimeout(r, 3000));Step 5 — Read the source code
Read all component source files. Look for:
- Missing responsive classes — no
sm:,md:,lg:,xl:prefixes (Tailwind) or equivalent media queries - Fixed widths that should be fluid
- Flex layouts that don't wrap or reflow
- Elements that should hide/show at different breakpoints
- Padding/margins that don't scale down
Step 6 — Produce the plan
Output a structured plan with:
- Current state table — breakpoint × what's broken
- Breakpoint strategy — which breakpoint is the mobile↔desktop switch point and why
- File-by-file changes — what to modify in each file
- New files needed — e.g. a mobile drawer, responsive variant
Common responsive patterns for navigation:
- Desktop nav → hamburger + drawer below the switch breakpoint
- Multi-column → stacked layout for content grids
- Hide secondary elements (announcements, labels) on small screens
- Accordion replaces mega menu on mobile
Step 7 — Implement (if asked)
Apply the changes, then:
- Build check — run the project build to verify no errors
- Re-screenshot — capture all breakpoints again with the same script
- View and verify — read each screenshot to confirm the fix
- Test interactions — if there are interactive elements (menus, drawers), use dev-browser to click/tap them and screenshot the result
// Example: testing a mobile menu
await page.click('button[aria-label="Open menu"]');
await new Promise(r => setTimeout(r, 400));
const buf = await saveScreenshot(await page.screenshot(), "audit-mobile-menu-open.png");- Update docs — if the component has design system documentation, update anatomy, behaviour, and file listings
Step 8 — Commit
Commit with a descriptive message noting the responsive changes:
feat(<Component>): add responsive layout with mobile <pattern>
- <file>: <what changed>
- <new file>: <what it does>
Breakpoint: <breakpoint> switches between mobile and desktop layoutDoes 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.

