Skip to main content
Agent skill

Wireframe Mobile Flow

A lo-fi multi-screen MOBILE flow wireframe — three or four phone frames laid out in a row on a board, showing a connected user flow (Onboarding → Home feed → Item detail → Confirm). Grey-box content inside each device, dashed connector arrows + numbered step labels between screens, and a couple of annotation callouts. Reads like an app flow pinned to a whiteboard before any pixels are committed. Use when the brief asks for "mobile wireframe", "app flow", "user flow wireframe", "lo-fi mobile", "low fidelity", "线框图", "移动端线框", or "App 流程".

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Wireframe Mobile Flow when an AI agent needs a reusable SKILL.md workflow for this job: A lo-fi multi-screen MOBILE flow wireframe — three or four phone frames laid out in a row on a board, showing a connected user flow (Onboarding → Home feed → Item detail → Confirm). Grey-box content inside each device, dashed connector arrows + numbered step labels between screens, and a couple of annotation callouts. Reads like an app flow pinned to a whiteboard before any pixels are committed. Use when the brief asks for "mobile wireframe", "app flow", "user flow wireframe", "lo-fi mobile", "low fidelity", "线框图", "移动端线框", or "App 流程".

When not to use it

Skip Wireframe Mobile Flow when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/wireframe-mobile-flow
# Save SKILL.md to ~/.claude/skills/wireframe-mobile-flow/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/wireframe-mobile-flow/SKILL.md. For a shared project, commit the folder at .claude/skills/wireframe-mobile-flow/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Wireframe Mobile Flow skill for this task: Skip the DESIGN.md if it pushes for finished UI. This skill is. Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Wireframe Mobile Flow Skill

Produce a single board showing a mobile app's user flow as a row of lo-fi phone frames. The point is the *flow* — how a user moves screen to screen — not the polish of any one screen. Keep the screens clean grey-boxes (not scribbly) but keep the connectors and annotations loose and informal.

## Workflow

1. **Skip the DESIGN.md** if it pushes for finished UI. This skill is deliberately low-fidelity: greyboxes, placeholder rects, and bars stand in for real content. Honor type tokens only loosely (system sans for the board, mono for labels and datelines). 2. **Pick the flow steps** from the brief — typically 3–4 connected screens like Onboarding → Home feed → Item detail → Confirm. Name each step so the connector arrows can carry a numbered, verb-first label ("① tap Start", "② open item", "③ add to cart"). 3. **Lay out the board**, in order: - **Board header** — bold sans title with a pinned "WIREFRAME v0.1 · MOBILE" tag (dashed border, slight rotation) and a mono dateline on the right (date / device / fidelity). - **Phone row** — 3–4 rounded device frames (~240–280px wide) in a horizontal row, each with a notch / status bar. Inside each frame put the greybox content for its step: hero image-placeholder (rect + X), title/price bars, list cards (thumbnail X + 2 text bars), category chips, a bottom tab bar, sticky CTA bars, a confirm checkmark — match the screen's role. - **Connectors** — dashed arrows between consecutive phones, each carrying a small mono step label describing the tap that advances the flow. - **Annotations** — 1–2 small sticky / callout notes pinned near a screen to flag intent ("hero must sell value in 3s", "checkout = 1 screen"). 4. **Write** a single HTML document: - `<!doctype html>` through `</html>`, CSS inline, no external JS, no external images (CSS/SVG placeholders only). - Use Inter / system-ui for the board and IBM Plex Mono for labels via Google Fonts; a light marker font is allowed for annotations only. - Defined dark device-frame borders, medium-grey content blocks on white screens, and a single accent color for arrows and annotations so the board reads clearly even as a small thumbnail. - `data-od-id` on the header, each phone screen, the connectors, and the annotations. 5. **Self-check**: - The three main phones are visible in a ~1280px viewport; the flow reads left-to-right. - Screens are clean greyboxes (not scribbly); connectors and stickies are the loose, informal parts. - No near-white-on-white regions — every block has a visible grey fill or border. If a screen renders blank as a thumbnail, raise the contrast.

## Output contract

Emit between `<artifact>` tags:

``` <artifact identifier="wireframe-slug" type="text/html" title="Wireframe — Title"> <!doctype html> <html>...</html> </artifact> ```

One sentence before the artifact, nothing after.

Intended uses

  • Skip the DESIGN.md if it pushes for finished UI. This skill is
  • Pick the flow steps from the brief — typically 3–4 connected screens
  • Lay out the board, in order:
  • Board header — bold sans title with a pinned "WIREFRAME v0.1 ·
  • Phone row — 3–4 rounded device frames (240–280px wide) in a
  • Connectors — dashed arrows between consecutive phones, each carrying
  • Annotations — 1–2 small sticky / callout notes pinned near a screen
  • Write a single HTML document:
  • <!doctype html> through </html>, CSS inline, no external JS, no
  • Use Inter / system-ui for the board and IBM Plex Mono for labels via
  • Defined dark device-frame borders, medium-grey content blocks on white
  • data-od-id on the header, each phone screen, the connectors, and the
  • Self-check:
  • The three main phones are visible in a 1280px viewport; the flow reads
  • Screens are clean greyboxes (not scribbly); connectors and stickies are
  • No near-white-on-white regions — every block has a visible grey fill or

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.