Mobile Design Os

Community

Xinvtech

mobile-design-os

Orchestrate the complete mobile product-design workflow across research, screenshot analysis, product framing, UX architecture, wireframes, visual direction, UI, design systems, prototypes, platform checks, design review, and optional code handoff. Use when Codex needs to take an iOS or Android idea through multiple design stages, resume an existing design run, decide which Mobile Design OS Skill should run next, validate cross-stage artifacts, or produce an evidence-honest end-to-end design package instead of an isolated screen.

Overview

Publisher	Xinvtech
Repository	`mobile-design-os`
Skill name	`mobile-design-os`
Stars	4
Forks	0
Bundled files	4
License	MIT
Links	Skill source Repository Homepage

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.
4 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 Design Os AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Xinvtech/mobile-design-os/tree/main/skills/mobile-design-os
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.

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-design-os .claude/skills/mobile-design-os

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mobile Design Os 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 Design Os 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 Design Os 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 Design OS

Run the smallest complete mobile-design chain that satisfies the requested outcome. Route work to the specialized Skills, preserve stable IDs and evidence between stages, and never let polished visuals erase unresolved product, platform, state, or validation gaps.

Establish the run

Determine:

Requested outcome: analysis, product framing, UX, visual concept, full design package, prototype, review, or implementation handoff.
Target platform and form factors.
Available inputs: product idea, screenshots, URLs, brand material, existing contracts, code, or runtime evidence.
Authorized scope: design only, prototype, or code changes.
Decisions that genuinely require the user, especially safety model, primary actor, MVP boundary, visual direction, framework override, and public license.

Create design-run.json from assets/design-run-template.json when the work crosses two or more stages or must be resumable. Read references/pipeline-contract.md before creating or updating the manifest.

Route to the required Skills

Read the selected Skill's SKILL.md completely before executing its stage. Do not load every Skill body when the request needs only one or two stages.

Need	Skill	Completion evidence
Discover or compare references	`mobile-reference-research`	Valid `reference-research.json`
Extract mechanics and Design DNA	`analyze-mobile-ui`	Valid `design-dna.json`
Frame product and MVP	`mobile-product-brief`	Valid `product-brief.json`
Define flows, objects, screens, and states	`mobile-ux-architect`	Valid `ux-architecture.json`
Establish low-fidelity hierarchy	`mobile-wireframe`	Valid `wireframe.json`
Explore and render visual UI	`mobile-ui-design`	User-selected, locked, valid `ui-design.json` when structured handoff is requested
Extract reusable tokens/components	`mobile-design-system`	Valid `design-system.json`
Model or render interaction behavior	`mobile-prototype`	Valid `prototype.json` and UI alignment report when UI exists
Decide and test native behavior	`mobile-platform-guidelines`	Valid `platform-guidelines.json`
Audit the chain	`mobile-design-review`	Valid `review.json` with an honest decision
Plan or scaffold implementation	`mobile-design-to-code`	Valid handoff plus actual build/test evidence when code is generated

Execute the full chain

For an end-to-end request, use this order while skipping only stages explicitly marked not-required:

Run mobile-product-brief to lock problem, audience, activation, core loop, MVP, trust boundaries, and unresolved decisions.
Run mobile-reference-research when references are missing or need comparison.
Run analyze-mobile-ui when screenshots or reference products must become traceable Design DNA.
Run mobile-ux-architect from the validated brief and reference decisions.
Run mobile-wireframe before visual styling when hierarchy or state pressure is nontrivial.
Run mobile-ui-design. Enforce exactly three comparable previews and stop at its user-choice gate. Do not select a visual direction unless the user explicitly delegates the choice.
After selection, lock the visual direction and complete rendered screens and the structured UI artifact.
Run mobile-design-system when downstream reuse or implementation tokens are needed.
Run mobile-prototype, then validate UI-to-prototype state and interaction alignment.
Run mobile-platform-guidelines for native behavior and device test cases.
Run mobile-design-review against the complete available chain.
Run mobile-design-to-code only when implementation or handoff is requested and the review decision permits it.

Update design-run.json after every stage. Preserve upstream Requirement, Flow, Screen, State, Token, Component, and evidence IDs; never silently regenerate identifiers at a downstream stage.

Enforce gates

Run every stage validator named by the selected Skill and fix structural failures before continuing.
Require a validated Product Brief before claiming UX completeness.
Require explicit state ownership and recovery before claiming UI completeness.
Require visualLock.status: locked and a user or user-delegated selection source before Design System or rendered prototype work.
Require UI-to-prototype alignment when both artifacts exist.
Keep screenshots and browser runners from proving runtime accessibility, lifecycle, permissions, sensors, persistence, delivery, or device behavior.
Keep a code handoff from proving that generated code builds or tests. Record the exact commands and results when code is generated.
Require no open P0 or P1 and no missing high-risk evidence before a pass; otherwise use conditional-pass, revise, or fail as defined by the review Skill.

Run python3 scripts/validate_design_run.py <path-to-design-run.json> --root <run-directory> before delivering a multi-stage run.

Stop only for material decisions

Pause when:

The user must choose among the three visual directions.
A decision changes safety, privacy, primary actor, core value loop, destructive behavior, or MVP scope.
A required input or authorization is unavailable.
The next step would claim external evaluation, physical-device evidence, production behavior, or a public license that has not actually been provided.

Otherwise proceed with a labeled assumption and record it in the manifest.

Deliver the run

Return:

Outcome and current stage decision.
Completed stages and validated artifact paths.
User decisions and labeled assumptions.
Open P0/P1 issues and untested high-risk behavior.
The next executable stage, or the exact external/device/user gate that remains.

Do not describe the chain as complete when a required stage is pending, awaiting user selection, blocked, or structurally valid but untested.

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 Design Os AI skill do?

Why use Mobile Design Os on TypingMind?

Because you install it once and use it with any model. Mobile Design Os 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 Design Os in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Xinvtech/mobile-design-os/tree/main/skills/mobile-design-os. 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 Design Os?

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 Design Os?

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

Is the Mobile Design Os 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

Auteur

NousResearch

OrganizationPopular

Design and build cinematic, award-level web pages.

Concept Diagrams

Generate flat, minimal educational SVG visuals as HTML.

Hyperframes

Render MP4/WebM videos from HTML compositions.

Ip As Logo

Design minimal cute IP mascot marks readable at 32px.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Mobile Design OS

Establish the run

Route to the required Skills

Execute the full chain

Enforce gates

Stop only for material decisions

Deliver the run

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now