mobile-app — Claude Code skill: what it does, how to install
This skill builds one mobile app screen inside an iPhone 15 Pro frame. Use it for HTML interface prototypes driven by a brief.
Apache-2.0 269 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill mobile-app -a claude-codeWhat mobile-app does
The skill produces a single mobile screen inside a realistic iPhone 15 Pro frame. It starts from assets/template.html, maps the active DESIGN.md tokens, and inserts one layout from references/layouts.md: Feed, Detail, Onboarding, Profile, Checkout, or Focus. The result is served through index.html.
Its workflow reads the seed, picks one screen job, fills the chosen layout with specific copy, then checks the device frame and interaction details. The review covers the Dynamic Island, status icons, home indicator, tap target size, accent use, and serif display type. External images are replaced with .ph-img placeholders.
A brief that mixes several flows must be reduced to one screen. The frame is already built into assets/template.html, so rebuilding it in the screen markup would conflict with the skill’s workflow.
What it helps with
- build one mobile app screen in HTML
- place a UI mockup inside an iPhone 15 Pro frame
- choose a layout for a feed, profile, or checkout screen
- check tap targets and accent usage
Example prompts for the agent
- Build one mobile app screen from this brief and save it as
index.html. - Create a Profile screen using the tokens in
DESIGN.md, while keeping the iPhone 15 Pro frame. - Make a Checkout screen with the Checkout archetype and remove the tab bar.
How to install mobile-app
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill mobile-app -a claude-code2Manually: put the files in place
~/.claude/skills/mobile-app/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mobile-app/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill mobile-app -a codex2Manually: put the files in place
.agents/skills/mobile-app/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill mobile-app -a cursor2Manually: put the files in place
.cursor/skills/mobile-app/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/mobile-app/SKILL.md2Manually: put the files in place
.github/skills/mobile-app/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill mobile-app -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/mobile-appManually: put the files in place
.devin/skills/mobile-app/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill mobile-app -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mobile-app
How do I install mobile-app in Claude Code?
Run npx skills add nexu-io/open-design --skill mobile-app -a claude-code, then use the skill at ~/.claude/skills/mobile-app/SKILL.md.
What does mobile-app do?
It creates one HTML mobile app screen inside an iPhone 15 Pro frame and fills one of six available screen archetypes.
Which screen archetypes does mobile-app include?
The skill includes Feed, Detail, Onboarding, Profile, Checkout, and Focus. Each result uses exactly one archetype.
Source text
SKILL.md · Apache-2.0
---
name: mobile-app
description: |
A mobile-app screen rendered inside a pixel-accurate iPhone 15 Pro frame
on the page. Built by copying the seed `assets/template.html` and pasting
one screen archetype from `references/layouts.md`. Use when the brief asks
for "mobile app", "iOS app", "Android app", "phone screen", or "app UI".
triggers:
- "mobile app"
- "ios app"
- "android app"
- "phone screen"
- "app ui"
- "app mockup"
- "移动端"
- "手机 app"
od:
mode: prototype
platform: mobile
scenario: design
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
craft:
requires: [state-coverage, animation-discipline]
---
# Mobile App Skill
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
1. **Read `assets/template.html`** end-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.
2. **Read `references/layouts.md`** so you know which 6 archetypes exist.
3. **Read the active DESIGN.md** — map its tokens to the six `:root` variables 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 `.num` class.
- **Display in serif** via `var(--font-display)`.
- **No external images** — use `.ph-img` placeholders.
© nexu-io · Apache-2.0 · nexu-io/open-design