mobile-app
A mobile-app screen authored at standard phone resolution (390×844) with responsive device adaptation, rounded corners, and no device frame. Use when the brief asks for "mobile app", "iOS app", "Android app", "phone screen", or "app UI".
- License 许可
- Apache-2.0
- 所属仓库
- zai-org/ZCode
- 最近更新
- 2026-11-13
- Stars
- ★ 8.7k
- Forks
- 2.7k
01 前言 Front Matter
- od
- { "mode": "prototype", "craft": { "requires": [ "state-coverage", "animation-discipline" ] }, "preview": { "type": "html", "entry": "index.html" }, "platform": "mobile", "scenario": "design", "design_system": { "requires": true, "sections": [ "color", "typography", "layout", "components" ] } }
- name
- mobile-app
- triggers
- [ "mobile app", "ios app", "android app", "phone screen", "app ui", "app mockup", "移动端", "手机 app" ]
- description
- A mobile-app screen authored at standard phone resolution (390×844) with responsive device adaptation, rounded corners, and no device frame. Use when the brief asks for "mobile app", "iOS app", "Android app", "phone screen", or "app UI".
02 资源文件 4
- 资产文件assets/template.html14.9 KB
- 参考文档example.html6.1 KB
- 参考文档references/checklist.md3.0 KB
- 参考文档references/layouts.md13.4 KB
03 SKILL.md 正文
<!-- Modified by ZCode: frameless 390x844 screen instead of a device frame. Derived from open-design 0.7.0 (Apache-2.0); see design-resources/NOTICE.md. -->
Mobile App Skill
Produce a single mobile-app screen mockup that defaults to standard phone resolution, with rounded corners, no device frame, and responsive behavior for tablet and desktop preview widths.
Resource map
mobile-app/
├── SKILL.md ← you're reading this
├── assets/
│ └── template.html ← seed: screen container + primitives (READ FIRST)
└── references/
├── layouts.md ← 6 screen archetypes (Feed / Detail / Onboarding / Profile / Checkout / Focus)
└── checklist.md ← P0/P1/P2 self-review
Workflow
Step 0 — Pre-flight
- Read
assets/template.htmlend-to-end through the<style>block. The screen container, status bar, home indicator, and tab bar are already drawn — do not re-implement them. - 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>.
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:
- Screen has rounded corners (44px)
- 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
- No device frame. No iPhone bezel, no Dynamic Island, no metallic rails. The screen itself has 44px rounded corners — that's enough to read as "phone".
- Default phone resolution. Screen is authored at 390×844 (iPhone 14/15 logical), but the HTML must also adapt when the host switches to tablet or desktop viewport.
- No permanently fixed outer shell. You may use 390×844 as the mobile authoring viewport, but the root app surface must have responsive constraints (
width: min(...),height: min(...), media queries, or equivalent) so it does not break at 834×1112 or 1440×900. - 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. - No emoji anywhere in the rendered screen. Not as icons, not as avatars, not as product images. Use
.ph-imgfor image placeholders and inline SVG for icons.
04 同仓库更多 Skills
plugin-mcp-ping
E2E workspace Plugin skill marker
e2e-ext-compat-plain
PLM-EXT-STORE fixture skill for e2e-ext-compat-plain.
e2e-ext-compat-ok
PLM-EXT-STORE fixture skill for e2e-ext-compat-ok.
e2e-ext-compat-installed
PLM-EXT-STORE fixture skill for e2e-ext-compat-installed.
e2e-ext-compat-future
PLM-EXT-STORE fixture skill for e2e-ext-compat-future.
e2e-store-skill-b
E2E store fixture skill b