Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Responsive Layout Screenshot QA: Fix Every Screen Size

    1

    Claude writes HTML and CSS without seeing the result, so pages often look fine in code and broken on a phone.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Responsive Layout Screenshot QA: Fix Every Screen Size

    Responsive Layout Screenshot QA: Fix Every Screen Size

    Example session with this skill installed

    Check if index.html is responsive. The mobile layout feels broken on small screens.

    • Read your context and instructions
    • Compiled the responsive layout screenshot
    • Generated the design tokens stylesheet

    I have rendered index.html at 360px, 768px, and 1280px widths using Playwright.

    Layout QA Results

    WHAT I SEE

    360px: The main headline is truncated on the right. A horizontal scrollbar is visible. The primary CTA button is partially covered by the footer.

    • 768px: Layout stacks correctly, but the navigation links are too close together for easy tapping.
    • 1280px: Everything renders as expected.

    MEASURED ISSUES

    WidthHorizontal ScrollSmall Text (<14px)Small Tap Targets (<44px)Overlaps
    360pxYes (392px wide)4 elements2 buttonsYes
    768pxNo0 elements5 linksNo
    1280pxNo0 elements0 elementsNo

    RANKED FIXES

    1. Fix Overflow: The .hero-container has a fixed width: 400px. Changed to max-width: 100%.
    2. Fix Overlap: Footer had position: absolute without a container height. Changed to standard document flow.
    3. Fix Tap Targets: Increased padding on .nav-link from 5px to 12px.

    EDITED CODE

    /* style.css */
    .hero-container {
      max-width: 100%;
      padding: 20px;
      box-sizing: border-box;
    }
    
    .nav-link {
      padding: 12px 16px;
      display: inline-block;
    }
    
    footer {
      position: relative;
      margin-top: 40px;
    }
    

    BEFORE / AFTER

    I re-rendered the page with the fixes.

    • Horizontal Scroll: 0 (Fixed)
    • Small Tap Targets: 0 (Fixed)
    • Visual: The headline now wraps correctly on the 360px view.

    Next steps

    1. Review the new shot-360.png to confirm the headline wrap looks aesthetically pleasing.
    2. Test the mobile navigation menu to ensure the increased hit areas don't crowd the logo.

    index.html

    CSS · design tokens

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Claude writes HTML and CSS without seeing the result, so pages often look fine in code and broken on a phone. This skill closes the loop: render, look, measure, fix, render again.

    What it does

    • Real rendering: an included Playwright script opens the page in headless Chromium at 360, 768 and 1280px, or widths you choose.
    • Screenshots Claude reviews: first-screen and full-page images per width, described from what is actually there.
    • Measured problems: horizontal scroll and the elements causing it, text under 14px, tap targets under 44px, overlapping controls, upscaled or oversized images and missing alt attributes.
    • Ranked fixes: broken first, then what hurts conversion, then polish, each with the smallest CSS or HTML change.
    • Before and after: re-renders the fixed page and compares the counts.

    How it works

    1. Give a URL or a local HTML file.
    2. Run the script and let Claude review the screenshots and report.
    3. Get the edited code and proof the fix worked.

    Needs Playwright and Chromium on your machine; without them only a code review is possible and it is labeled unverified. Checks layout, not visual taste or copy.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 10 days ago

    Requires

    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed10 days ago

    What's inside

    Frequently Asked Questions

    Python, Playwright and its Chromium browser. Install steps are in the skill.

    Yes, any URL your machine can reach, or a local file.

    Only what a fix needs; copy, colors and branding stay unless they cause the problem.

    No. This renders and measures the page in a real browser and proves fixes with new screenshots.

    They stay in a folder on your machine.

    Yes. It checks the rendered page in a browser, so Tailwind, Bootstrap, plain CSS or any framework that outputs HTML works; fixes are written in the style your code already uses.

    New in Testing & Debugging