Mobile Design System

Community

Xinvtech

mobile-design-system

Extract, define, and govern reusable mobile design tokens, foundations, components, themes, accessibility semantics, and platform variants from Design DNA, UI specifications, or an existing app. Use when Codex needs a standalone mobile design system instead of product-specific screen styling, or when a UI package must become a maintainable implementation library.

Overview

Publisher	Xinvtech
Repository	`mobile-design-os`
Skill name	`mobile-design-system`
Stars	4
Forks	0
Bundled files	6
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.
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 Design System 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-system
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-system .claude/skills/mobile-design-system

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

Use it in TypingMind

Enable Mobile Design System 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 System 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 System 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 System

Turn visual intent and repeated UI behavior into a small, semantic, accessible system that can survive new screens and platform variants.

Establish the input contract

Prefer design-dna.json, ui-design.json, and the selected visual-direction.md. For new or replacement visual work, require the ui-design.json visual lock and consume its selected style family, reference IDs, theme variant, and exact theme tokens. Preserve provenance: inherited values come from an upstream artifact, specified values are deliberate target decisions, and estimated values remain estimates. Never turn a screenshot guess into an observed token.

Build the system in layers

Define foundations: color roles, type roles, spacing, shape, elevation/material, iconography, motion, content voice, and accessibility rules.
Copy the locked reference fingerprint into the system thesis and keep the selected semantic theme tokens as the renderer source of truth.
Define tokens as primitive → semantic → component where the system benefits from the extra layer. Prefer semantic roles over raw values in screen contracts.
Define components by user meaning and repeated anatomy, not by a generic “card” bucket.
Specify default, pressed, focused, selected, disabled, loading, success, warning, failure, stale, expired, and permission states as applicable.
Record light/dark, compact/regular, iOS/Android, large-text, keyboard, Reduce Motion, and localization variants.
Establish governance: naming, deprecation, change ownership, contrast/target-size checks, and acceptance signals.

Read references/system-rules.md for token and component boundaries. Use references/design-system-schema.md before creating structured output.

Produce and validate

Create:

design-system.md using assets/design-system-template.md.
design-system.json using assets/design-system-template.json.

Run python3 scripts/validate_design_system.py <path-to-design-system.json> and fix every error. When a UI artifact is available, also validate that every referenced UI token and component has a system definition.

If ui-design.json contains visualExploration, run the validator with --source-ui and reject any Design System whose visualLock is missing, unlocked, or inconsistent with the chosen direction. Never rebuild the system from Design DNA alone after a visual lock exists.

Enforce the output order

System thesis, scope, and provenance.
Foundations and semantic tokens.
Component contracts and state behavior.
Themes, platform variants, and accessibility pressure.
Governance, coverage, open questions, and confidence.

Do not finish with a color palette alone, a component gallery with no state semantics, or a system that cannot explain how a new screen consumes its roles.

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

Why use Mobile Design System on TypingMind?

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

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

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 System?

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

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

Ip As Logo

NousResearch

OrganizationPopular

Design minimal cute IP mascot marks readable at 32px.

Mono Color

Generate one- or two-ink editorial print poster images.

Pretext

Build creative browser demos with DOM-free text layout.

Sketch

Throwaway HTML mockups: 2-3 design variants to compare.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Mobile Design System

Establish the input contract

Build the system in layers

Produce and validate

Enforce the output order

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now