iphone13mini-ui
Skill1 starsChanged 40 days agoMITView on GitHub
Build or fix web UI for iPhone 13 mini Safari: 375px layouts, overflow, touch controls, safe areas, toolbar or keyboard overlap, and screenshot comparison. Use for small-iPhone web UI work, not native iOS apps or general desktop styling.
In this repository29 other files it gives its agents.
- architectSkill
- audit-discoverySkill
- audit-initSkill
- audit-nextSkill
- audit-resolutionSkill
- audit-statusSkill
- audit-triageSkill
- audit-verificationSkill
- code-to-prdSkill
- codex-ubuntu-serverSkill
- copilot-review-customizerSkill
- create-pluginSkill
- create-skillSkill
- debugSkill
- deep-reviewSkill
- design-promptsSkill
- diagnose-sessionSkill
- feature-scatteringSkill
- human-execution-runbookSkill
- humanizerSkill
- init-repo-instructionsSkill
- inspect-pluginSkill
- install-agent-pluginsSkill
- local-wikiSkill
- recoverSkill
- review-feedbackSkill
- review-repo-instructionsSkill
- uncompromising-handoverSkill
- update-pluginSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 8
Read and apply the delivery contract within this skill's scope and authorization.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
iPhone 13 mini UI
Read and apply the delivery contract within this skill's scope and authorization.
Workflow
I reproduce the requested route and interaction using the project's existing dev
server and styles. I use Playwright WebKit with iPhone 13 Mini; when unavailable,
I use Chromium explicitly and identify it in the result. Neither runs iOS Safari.
I inspect the rendered page and DOM at 375 CSS px, then address the actual cause: flex/grid minimum sizes, overflowing content, text wrapping, hit areas or viewport positioning. I preserve intentional horizontal scrollers and truncation rather than hiding overflow on the whole page.
For an implementation request, I capture the affected state before and after the change. I check landscape, alternate themes or keyboard states when the change can affect them. Toolbar, keyboard and iOS font behavior need the real device; missing device access does not block local layout work.
Local capture
I set SKILL_DIR to this file's directory and URL to the running page.
python3 -B "$SKILL_DIR/scripts/capture.py" local --url "$URL" --output out/iphone/page.pngI use --ready-selector or --ready-js for application readiness,
--orientation landscape for rotation and --viewport WIDTHxHEIGHT for measured
geometry. I inspect the PNG and its JSON: response status, loaded resources,
viewport and browser version. For stateful flows I reuse the project's Playwright
setup; a fresh capture context has no existing login or application storage.
For a DOM scan I run ui_audit.py --url "$URL" --json out/iphone/audit.json.
Its findings are leads: I confirm the affected element and interaction before
changing CSS. Other flags are in each helper's --help.
Targeted references
- For setup, CSS decisions or interpreting the audit, I read browser notes.
- For phone capture or comparing a supplied screenshot, I read device and comparison.
I report the change, the environment and state actually checked, and any relevant phone behavior still unverified. I link useful artifacts rather than repeating capture metadata.
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.

