Mobile App Skill
SkillMediaThe mobile-app skill guides an AI agent to build a single mobile app screen mockup shown inside a pixel-accurate iPhone 15 Pro frame. It works by copying a ready-made HTML template, filling in one of six screen layouts such as a feed, profile, or c
Available today. Use it from your connected AI after setup.
No other account needed.
Have a project with an active design system covering color, typography, layout, and components.
Then ask your AI: use the Mobile App Skill skill
What your AI can do with it
- Renders a mobile app screen inside a pixel-accurate iPhone 15 Pro frame
- Provides six screen archetypes: Feed, Detail, Onboarding, Profile, Checkout, and Focus
- Maps a project's design-system colors and fonts onto template variables
- Includes pre-drawn Dynamic Island, status bar icons, home indicator, and tab bar
- Runs a self-review checklist covering tap-target sizes and accent color limits
- Triggers on briefs mentioning mobile app, iOS app, Android app, phone screen, or app UI
Getting started
- Have a project with an active design system covering color, typography, layout, and components.
- Have the agent read the seed assets/template.html, the six archetypes in references/layouts.md, and the active DESIGN.md.
- Copy assets/template.html to the project root as index.html and replace the six :root variables with the design system's tokens.
- Pick exactly one screen archetype matching the brief, paste its block into the content area, and fill the bracketed text with real copy.
- Run the self-review checklist in references/checklist.md, checking the device frame details, 44px tap targets, and accent color limits.
What this skill tells your AI
The instructions your AI receives, as published by nexu-io/open-design in design-templates/mobile-app/SKILL.md and read by ahel’s review.
Produce a single mobile-app screen mockup, framed inside a real-feeling iPhone 15 Pro device.
Resource map
mobile-app/
├── SKILL.md ← you're reading this
├── assets/
│ └── template.html ← seed: device frame + screen primitives (READ FIRST)
└── references/
├── layouts.md ← 6 screen archetypes (Feed / Detail / Onboarding / Profile / Checkout / Focus)
└── checklist.md ← P0/P1/P2 self-review (anti-fake-device)
Workflow
Step 0 — Pre-flight
- Read
assets/template.htmlend-to-end through the<style>block. The Dynamic Island, status bar SVG icons, home indicator, side rails, and tab bar are all already drawn in HTML/SVG — do not re-implement them inline on each screen. - Read
references/layouts.mdso you know which 6 archetypes exist. - Read the active DESIGN.md — map its tokens to the six
:rootvariables in the seed.
Step 1 — Copy the seed
Copy assets/template.html to the project root as index.html. Replace the six :root variables with the active design system's tokens. Replace the page <title> and the caption above the device.
Step 2 — Pick exactly one archetype
| Brief language | Use |
|---|---|
| feed, inbox, timeline, list, messages, notifications | A — Feed |
| article, post, item, recipe, song, product, song detail | B — Detail |
| sign-up, welcome, intro, walkthrough, tour | C — Onboarding |
| profile, account, user page, someone's bio | D — Profile |
| checkout, payment, order, form, settings step | E — Checkout |
| timer, map, dashboard widget, single big number | F — Focus / hero card |
A mobile screen does one job. If the brief seems to combine two, ship one screen and offer the other as a follow-up.
Step 3 — Paste and fill
Copy the archetype block from layouts.md into <main class="content">, replacing the placeholder card. Fill bracketed text with real, specific copy from the brief. Drop the <nav class="tabbar"> block entirely for archetypes that don't show one (B, C, E).
Step 4 — Self-check
Run through references/checklist.md. Pay extra attention to:
- Frame still has the Dynamic Island, status bar SVGs, and home indicator
- Tap targets ≥ 44px
- One accent, used ≤ 2× on the screen
- Display headings still use
var(--font-display)(serif)
Step 5 — Emit the artifact
<artifact identifier="mobile-slug" type="text/html" title="Mobile — Screen Name">
<!doctype html>
<html>...</html>
</artifact>
One sentence before describing what's there. Stop after </artifact>.
Hard rules
- The phone is real. Dynamic Island gap, SVG status icons, home indicator. The seed protects all three — don't rewrite the frame.
- Single screen, single job. No multi-tab tours, no spliced flows.
- Accent budget = 2. One active tab + one primary action is the default.
- Numerics in mono via
.numclass. - Display in serif via
var(--font-display). - No external images — use
.ph-imgplaceholders.
Signals
- GitHub stars
- 98k
- Forks
- 11k
- Last commit
- Sep 2026
Others that do the same job
Questions
- When should this skill be used?
- When the brief asks for a "mobile app", "iOS app", "Android app", "phone screen", or "app UI". It also triggers on "app mockup" and related phrases.
- What screen types are available?
- Six archetypes: Feed (lists, timelines, messages), Detail (articles, products), Onboarding (sign-up, walkthrough), Profile (account, bio), Checkout (payment, forms), and Focus (timers, hero cards).
Advanced
- Item type
- skill
- Key
mobile-app-2- Source
- github.com/nexu-io/open-design