More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Phoneproof: UI reviewed on a real phone, with proof

    1

    Brand locked first, two or three mockups served to a real phone, tweaks from screenshots, a worst-case data and keyboard pass, then headless desktop and mobile screenshots before a change is called done.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Phoneproof: UI reviewed on a real phone, with proof

    Phoneproof: UI reviewed on a real phone, with proof

    Example session with this skill installed

    Phoneproof, review the profile page on mobile before I send it to the client for approval.

    • Read your context and instructions
    • Compiled the phoneproof

    Reviewed /profile (example app) on a real phone via preview deploy, then ran the worst-case toggle and keyboard and screen-reader walks.

    Findings (5, all fixed before review)

    #FindingSourceWCAG 2.2Fix
    1Page zooms when tapping the email fieldReal phonen/aInput font-size 14px to 16px
    2"Alexandria Montgomery-Fitzgerald" overflows the cardWorst case1.4.10 ReflowWrap long names, clamp to 2 lines
    3Zero-items state shows an empty white boxWorst casen/aEmpty state with one action
    4Focus ring gone on the Save buttonKeyboard walk2.4.7 Focus VisibleVisible focus style restored
    5Edit icon button has no nameScreen reader4.1.2 Name, Role, Valuearia-label "Edit profile"

    Proof

    • Playwright, test account, network idle: desktop and mobile screenshots for each of the 5 fixes.
    • Worst-case toggle screenshotted in both states.
    • Each behaviour change has a test; e2e passes at mobile width.

    Next steps

    • Send the preview link and the 10 screenshots to the client for approval.
    • After approval, port the profile changes to the main app and run the copy sweep.

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

    About this skill

    A screen gets approved on a laptop, then breaks on a phone: form fields zoom on tap, a long name overflows the card, the focus ring disappears for keyboard users. Screenshots of tidy demo data hide all of it. Phoneproof gives your agent a review loop where a UI change is only called done after it was seen on a real device and proven in screenshots.

    What it does

    • Brand lock stores palette, fonts, logo and tone as design tokens and a /brand page before any building starts.
    • Mockups first produces two or three clickable concepts, desktop and mobile, for the reviewer to pick before wiring.
    • Real phone review serves the build over LAN, a quick tunnel (only when asked) or a preview deploy.
    • Screenshot tweaks turns "screenshot plus one line" into a direct edit, one instruction per commit.
    • Worst-case and access gate adds a dev-only worst-case data toggle and runs keyboard and screen-reader walks, each finding tied to a WCAG 2.2 criterion.
    • Screenshot proof uses Playwright to capture desktop and mobile viewports for every change.

    How it works

    1. Lock the brand or the native reference you want to match.
    2. Mock up 2 or 3 concepts and get one approved.
    3. Review on a real phone and apply tweaks from screenshots.
    4. Gate with worst-case data, keyboard and screen-reader passes.
    5. Prove each change with headless screenshots, then port in phases and run a polish pass (copy, PWA, SEO, assets, accessibility, performance).

    Frameworks & tools

    Playwright, cloudflared quick tunnel, Vercel preview deploys, VoiceOver or NVDA, Canva brand kit, Google Stitch, pdftoppm or PyMuPDF.

    Why this beats prompting it yourself

    A plain prompt edits the UI and says it looks good. Phoneproof does not ask for approval until the worst-case toggle, keyboard walk and screenshots are done, and it carries guards from real incidents such as the iOS zoom on inputs under 16px.

    Use cases

    • UI revamps that should feel native on a phone.
    • PWA polish for manifest, service worker and safe areas.
    • Client site polish for speed, SEO, accessibility and copy.

    Known limitations

    Not for logic bugs with no visual symptom or pixel-perfect handoff from a finished design file. Real-phone review needs a device on the same network or a preview deploy.

    Not for logic bugs with no visual symptom or pixel-perfect handoff from a finished design file. Real-phone review needs a device on the same network or a preview deploy.

    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 29 days ago

    Requires

    Playwright
    cloudflared
    Vercel
    VoiceOver or NVDA
    Canva
    Google Stitch
    pdftoppm or PyMuPDF

    Permissions

    Browser
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    A web app or PWA you can run locally, and a phone for review. Playwright is used for screenshot proof, and a test account if the page needs a login.

    Only when you ask. Default review is localhost or LAN; a quick tunnel is opened on request and stopped when the review ends, and a preview deploy is used when auth or someone else's phone is involved.

    It will not call a change done until it ran the worst-case data toggle, keyboard and screen-reader walks, and captured desktop and mobile screenshots.

    SKILL.md, the skill file your agent reads, and LICENSE.md.

    New in Frontend & Web Apps