Ios Simulator Build Run

Community

milisp

ios-simulator-build-run

Build an iOS app and run it on the Simulator, then read build errors, logs and screenshots. Use when asked to build, run, launch, test or debug an iOS/iPadOS app, or when xcodebuild fails.

Overview

Publisher	milisp
Repository	`mcp-linker`
Skill name	`ios-simulator-build-run`
Stars	345
Forks	42
Bundled files	Instructions only
License	AGPL-3.0
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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by milisp on GitHub. Read the source before you install it.

Installation

Install the Ios Simulator Build Run 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/milisp/mcp-linker/tree/main/plugins/ios/skills/ios-simulator-build-run
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/milisp/mcp-linker/tree/main/plugins/ios/skills/ios-simulator-build-run

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

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/milisp/mcp-linker.git /tmp/mcp-linker
mkdir -p .claude/skills
cp -r /tmp/mcp-linker/plugins/ios/skills/ios-simulator-build-run .claude/skills/ios-simulator-build-run

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

Use it in TypingMind

Enable Ios Simulator Build Run 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 Ios Simulator Build Run 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 Ios Simulator Build Run 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.

Build and run on the iOS Simulator

Prefer the XcodeBuildMCP tools from this plugin; fall back to xcodebuild and xcrun simctl when the MCP server is unavailable.

Workflow

Discover: find the .xcworkspace / .xcodeproj (prefer the workspace when both exist), then list schemes and available simulators. CLI fallback:
- xcodebuild -list -workspace App.xcworkspace
- xcrun simctl list devices available
Pick a destination: choose one simulator and reuse it for the whole session. Boot it if needed (xcrun simctl boot <UDID>).

Build: with the MCP server use its simulator build tools. CLI fallback:


xcodebuild -workspace App.xcworkspace -scheme App \
  -destination 'platform=iOS Simulator,id=<UDID>' \
  -derivedDataPath build/DerivedData build

Install and launch: use the MCP build-and-run tool, or xcrun simctl install <UDID> <path/to/App.app> then xcrun simctl launch <UDID> <bundle-id>.
Verify: take a screenshot (xcrun simctl io <UDID> screenshot out.png) and capture logs (xcrun simctl spawn <UDID> log stream --predicate 'subsystem == "<bundle-id>"'). To interact with the running app, switch to the ios-simulator-ui-automation skill.

Reading failures

Read the first error: line, not the last; later errors are usually cascades.
Filter raw output with grep -E "error:|warning:|\*\* BUILD", or pipe through xcbeautify if installed.
"No such module": resolve packages (xcodebuild -resolvePackageDependencies) and rebuild for the same destination.
Signing errors on a simulator build: add CODE_SIGNING_ALLOWED=NO. For device or archive signing see ios-signing-troubleshooting.
Stale state: delete the derived data folder you passed with -derivedDataPath before blaming the code.

Tests

xcodebuild test -workspace ... -scheme ... -destination 'platform=iOS Simulator,id=<UDID>' -resultBundlePath build/Test.xcresult then inspect failures with xcrun xcresulttool get test-results summary --path build/Test.xcresult.

Rules

Never hand-edit project.pbxproj unless there is no alternative; prefer Xcode, XcodeGen or Tuist configuration.
Keep derived data inside the repo's ignored build directory so runs stay reproducible.

Frequently asked questions

What does the Ios Simulator Build Run AI skill do?

Build an iOS app and run it on the Simulator, then read build errors, logs and screenshots. Use when asked to build, run, launch, test or debug an iOS/iPadOS app, or when xcodebuild fails.

Why use Ios Simulator Build Run on TypingMind?

Because you install it once and use it with any model. Ios Simulator Build Run 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 Ios Simulator Build Run in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/milisp/mcp-linker/tree/main/plugins/ios/skills/ios-simulator-build-run. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ios Simulator Build Run?

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 Ios Simulator Build Run?

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

Is the Ios Simulator Build Run AI skill free?

Yes. It is published on GitHub by milisp under the AGPL-3.0 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

Build and run on the iOS Simulator

Workflow

Reading failures

Tests

Rules

Frequently asked questions

Related AI Skills

Set up your own AI workspace now