- Home
- Skills
- Mobile Development
- Design QA: Device Frame
Design QA: Device Frame
One self-contained HTML phone frame (iOS 390x844, Android 412x915) with safe areas, made for pixel comparisons and polished presentations.
$7
Works with the AI Agents you already use
Design QA: Device Frame
Example session with this skill installed
Put my checkout screen markup into an iOS and an Android frame with an app bar titled Checkout and a Continue button, capture both for pixel comparison, and give me one presentation image.
- Read your context and instructions
- Compiled the design qa
- Generated the UI component
1. Framed copy
Copied S/assets/frame.html to prototype/checkout.html and pasted your markup into <main id="slot">. Colours now use var(--frame-*) instead of hard-coded hex. Only .content scrolls; status bar, app bar, safe areas and the bottom button stay fixed.
2. Options (URL parameters)
?device=ios&appbar=1&title=Checkout&cta=Continue (and device=android for Android). No changes to --sa-top / --sa-bottom yet; adjust them from a real screenshot of the target device if you compare against one.
3. Captures for metrics (bare mode, one command per device, query matches --vp)
python3 S/scripts/snapshot.py "prototype/checkout.html?device=ios&appbar=1&title=Checkout&cta=Continue" --name cand --out .design-qa/checkout/runs/20261114-1600-1 --vp ios --dom --axe
python3 S/scripts/snapshot.py "prototype/checkout.html?device=android&appbar=1&title=Checkout&cta=Continue" --name cand --out .design-qa/checkout/runs/20261114-1600-1 --vp android --dom --axe
No frame/viewport mismatch warnings.
4. Presentation image (show mode, not for metrics)
python3 S/scripts/snapshot.py "prototype/checkout.html?device=ios&mode=show&appbar=1&title=Checkout&cta=Continue" --name show --out .design-qa/checkout/present --vp 520x980 --full
Files
.design-qa/checkout/runs/20261114-1600-1/cand@390x844.png,cand@412x915.png(+ .dom.json, .axe.json, cand.source.json).design-qa/checkout/present/show@520x980.png
Masks for comparing with real phone screenshots (system chrome; add the measured app bar and button heights):
390x844:0,0,390,47;390x844:0,810,390,34;412x915:0,0,412,24
frame.html
TSX · React component
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
Mobile prototypes built as plain HTML rarely match a phone screenshot. The screen size is off, the status bar and home indicator are missing, and the content scrolls under bars that should stay fixed.
This skill gives your agent one dependency-free frame.html:
- iOS 390x844 or Android 412x915 screen with status bar, safe areas and home indicator
- Optional in-app webview header and a native bottom-button placeholder
- Light and dark colour variables you can map to your tokens
- Bare mode renders exactly the viewport, so captures compare 1:1 with references
- Show mode adds a phone body for stakeholder presentations
The skill states the key rule (never measure the presentation mode) and includes deterministic capture commands with warnings for mismatched devices. It also gives the masks to use against real device screenshots. Every measurement is a CSS variable, so you adjust it from a screenshot instead of rewriting the layout.
What you get
assets/frame.html: self-contained frame with no external requests, English only, URL-parameter drivenSKILL.md: a 7-step workflow (copy, paste markup, options, adjust, capture for metrics, capture for show, mask)references/device-specs.md: parameters, CSS variables, default colours, mask SPECs, verified behaviourscripts/snapshot.py: deterministic capture with frame and device mismatch warnings
Permissions / network
frame.htmlmakes no network requests. Captures open only the file you pass and what your markup loads- Writes only your framed copy and the capture folder you choose
Part of the Design QA set with Fidelity Check, Reference Capture and Designer Judge. Works on its own.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.
Native controls (back button, bottom button, keyboard, popups) are visual placeholders. Safe-area and bar heights are typical values that vary by model, so adjust them from a screenshot. Not tested on physical devices or inside real in-app webviews.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
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 1 day ago
Nothing to install. It runs in your AI agent.
- Optional
Python 3.10+Playwright with Chromium
Only needed for captures. Viewing frame.html needs just a browser.
Permissions
File Scopes
frame.html makes no network requests. Terminal and Browser are only used for optional captures: headless Playwright Chromium opens the local file you pass (plus whatever your own markup loads). Install contacts PyPI and the Playwright CDN. Writes only your framed copy and the capture folder you choose.