Mobile Wireframe logo

Mobile Wireframe

Community
Xinvtech
mobile-wireframe

Convert a validated mobile UX architecture into low-fidelity screen and interaction structure before visual styling. Use when Codex needs wireframes, layout hierarchy, content priority, task-state coverage, overlay behavior, or a visual-agnostic handoff between UX architecture and UI design.

Overview

PublisherXinvtech
Repositorymobile-design-os
Skill namemobile-wireframe
Stars
4
Forks
0
Bundled files
6
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Xinvtech on GitHub. Read the source before you install it.

Installation

Install the Mobile Wireframe AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Xinvtech/mobile-design-os/tree/main/skills/mobile-wireframe
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Xinvtech/mobile-design-os.git /tmp/mobile-design-os
mkdir -p .claude/skills
cp -r /tmp/mobile-design-os/skills/mobile-wireframe .claude/skills/mobile-wireframe
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mobile Wireframe in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Mobile Wireframe on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Mobile Wireframe is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Mobile Wireframe

Define the screen skeleton and interaction hierarchy without choosing colors, typography, imagery, or decorative style.

Establish the input contract

Prefer ux-architecture.json plus product-brief.json. Validate upstream artifacts when validators exist. Preserve upstream Requirement, Flow, Screen, and State IDs. If the architecture is incomplete, record the gap rather than inventing a polished screen.

Build the wireframe

For each screen:

  1. State the single user question and primary task.
  2. Order the safe-area, navigation, context, content, action, and feedback regions.
  3. Assign each region a semantic role, content pressure, component role, and state behavior.
  4. Mark fixed, scrollable, sticky, keyboard-avoiding, sheet, dialog, and system-handoff behavior.
  5. Map entry, exit, primary action, secondary actions, and interruption recovery.
  6. Cover every upstream state; distinguish state changes from new screens.

Use neutral boxes and labels in visual artifacts. A wireframe may specify hierarchy, density, copy length, and interaction intent, but must not pretend to establish final tokens or visual direction.

Check the core flow

Trace at least one critical before/during/after path and one failure or interruption path. Verify that the primary action remains reachable, content identity survives errors, destructive actions have a consequence boundary, and system surfaces have in-app fallbacks.

Read references/wireframe-rules.md before finalizing regions and references/wireframe-schema.md before creating JSON.

Produce and validate

Create:

Run python3 scripts/validate_wireframe.py <path-to-wireframe.json> and fix every error. When an upstream UX file is available, also run python3 scripts/validate_wireframe.py <path-to-wireframe.json> --source-ux <path-to-ux-architecture.json> to check screen and state coverage.

Enforce the output order

  1. Source contract and assumptions.
  2. Navigation and flow skeleton.
  3. Screen inventory and region contracts.
  4. State, overlay, keyboard, and system-surface behavior.
  5. Traceability and unresolved decisions.

Do not finish with a styled mockup disguised as a wireframe or with a screen inventory that omits states and recovery.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Mobile Wireframe AI skill do?

Convert a validated mobile UX architecture into low-fidelity screen and interaction structure before visual styling. Use when Codex needs wireframes, layout hierarchy, content priority, task-state coverage, overlay behavior, or a visual-agnostic handoff between UX architecture and UI design.

Why use Mobile Wireframe on TypingMind?

Because you install it once and use it with any model. Mobile Wireframe is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Mobile Wireframe in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Xinvtech/mobile-design-os/tree/main/skills/mobile-wireframe. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Mobile Wireframe?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Mobile Wireframe?

As many as you like. As long as a model supports skills, you can use Mobile Wireframe with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Mobile Wireframe AI skill free?

Yes. It is published on GitHub by Xinvtech under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇