Buildable Mobile Builder

Community

suntay44

buildable-mobile-builder

Generate or adapt a local-first Buildable mobile prototype from an app spec, archetype, UI pattern, design playbook, or mobile golden template. Use for Buildable Expo/React Native implementation; do not use for ordinary mobile debugging or unrelated React Native edits.

Overview

Publisher	suntay44
Repository	`buildable-plugin-skills`
Skill name	`buildable-mobile-builder`
Stars	54
Forks	8
Bundled files	1
License	MIT
Links	Skill source Repository

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.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by suntay44 on GitHub. Read the source before you install it.

Installation

Install the Buildable Mobile Builder 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/suntay44/buildable-plugin-skills/tree/main/skills/mobile-builder
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/suntay44/buildable-plugin-skills.git /tmp/buildable-plugin-skills
mkdir -p .claude/skills
cp -r /tmp/buildable-plugin-skills/skills/mobile-builder .claude/skills/buildable-mobile-builder

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

Use it in TypingMind

Enable Buildable Mobile Builder 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 Buildable Mobile Builder 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 Buildable Mobile Builder 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.

Buildable Mobile Builder Skill

Use this skill to generate or adapt local mobile prototypes.

Resolve all referenced paths from the Buildable plugin or repository root.

Reference Loading Contract

Mandatory order:

Read .buildable/phase-plan.toon first when present. It is a summary: retrieve omitted details (such as full design rules or expected files) from the authoritative .buildable/phase-plan.json as needed. Without a saved plan, read buildable-app-spec.json. Reuse the plan for unchanged requirements rather than re-planning or reading all formats.
Load only appSpec.references.
Load current project files only as needed for the requested change.
Do not load web templates or unrelated mobile archetypes.
Load starter source only for the selected template and only when generating or editing it.

Default Stack

Expo
React Native
TypeScript
NativeWind
Expo Router when appropriate
local/mock data

Workflow

Read the saved plan/app spec from the planner handoff.
Check appSpec.planAudit.checks before editing; treat blocked/failed checks as gates, not suggestions.
If questionsNeeded is true, ask the user before generating.
Apply appSpec.designSystem for visual tone, density, palette intent, touch layout rules, component rules, accessibility, and anti-patterns.
Apply appSpec.blocks as reusable micro-template guidance. Selected block docs are references to adapt to the current entity/design system, not generic code to paste blindly.
If appSpec.auth.requested is true, implement the local/mock auth shape first and keep any named provider behind the auth seam.
Load only the references listed in the app spec.
If the template is generic-app, use the selected archetype reference to shape screens and entities instead of loading unrelated mobile templates.
Generate touch-first screens and local state.
Validate navigation, touch targets, and state coverage.
Run buildable review from the selected app workspace when the CLI is available.

Build Order

Create typed entities and local sample data.
Build the first mobile screen around the main daily workflow.
Add navigation only when the screen graph requires it.
Add empty, completed, validation, and confirmation states as appropriate.
Review against the selected mobile quality rubric.

Guardrails

Do not add accounts, push notifications, external APIs, or backend services unless requested.
Keep the mobile app runnable locally.

Bundled files

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

agents/openai.yaml1 KB

Frequently asked questions

What does the Buildable Mobile Builder AI skill do?

Why use Buildable Mobile Builder on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/suntay44/buildable-plugin-skills/tree/main/skills/mobile-builder. 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 Buildable Mobile Builder?

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 Buildable Mobile Builder?

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

Is the Buildable Mobile Builder AI skill free?

Yes. It is published on GitHub by suntay44 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

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Debugging

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Openclaw Live Updater

openclaw

OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Buildable Mobile Builder Skill

Reference Loading Contract

Default Stack

Workflow

Build Order

Guardrails

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now