SkillsAdd

xenodium/emacs-skills

xcode-run-simulator

This skill should be used when the user invokes "/xcode-run-simulator" to build the current Xcode project, install the app on an iOS Simulator, and launch it.

First seen Jun 22, 2026

Installation

$ npx skills add xenodium/emacs-skills --skill xcode-run-simulator
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from xenodium/emacs-skills · top by installs.

npx skills add xenodium/emacs-skills
emacsclient 105 describe 85 dired 83 open 80 select 78 highlight 77 file-links 69 gnuplot 66 plantuml 48 mermaid 48

Browse all from xenodium/emacs-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 135
Default branch main
Open issues 5
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,244 B
  • docs SUMMARY.md 185 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 9 installs

SKILL.md

Build + run on iOS Simulator

Build the Xcode workspace or project under the current working directory and launch it on an iOS Simulator. If a simulator is already booted, that one is used. Otherwise the latest available iPhone simulator is booted automatically and Simulator.app is brought to the foreground.

How to run

The shared agent-skill-xcode.el lives in the sibling xcode-shared directory at skills/xcode-shared/agent-skill-xcode.el in the emacs-skills plugin. All four /xcode-* skills load it from there.

emacsclient --eval "(progn (load \"/path/to/skills/xcode-shared/agent-skill-xcode.el\" nil t) (agent-skill-xcode-run-simulator :project-dir \"$(pwd)\"))"

The function:

  • Locates the workspace/project and picks a scheme (same heuristic as /xcode-build-simulator).
  • Picks a simulator: first booted iOS simulator if any; else the latest available iPhone (boots it and opens Simulator.app).
  • Runs xcodebuild build against the simulator's specific UDID.
  • Reads BUILTPRODUCTSDIR / WRAPPERNAME / PRODUCTBUNDLE_IDENTIFIER from -showBuildSettings -json.
  • Installs (xcrun simctl install) and launches (xcrun simctl launch).
  • Returns a multi-line status string with the bundle id, simulator UDID, .app path, install result, and launch result. On build failure, returns the same error format as /xcode-build-simulator.

Rules

  • Pass the agent's current working directory as :project-dir via $(pwd).
  • The shared elisp lives under xcode-shared/agent-skill-xcode.el — load it from there.
  • Run via the Bash tool with a single emacsclient --eval invocation. Builds can take minutes; consider extending the Bash timeout if known to be slow.
  • Report the returned status string verbatim. It already contains everything the user needs.
  • Do not try to choose a different simulator if one is already booted — the whole point is reuse.
  • If the build fails, point at the truncated tail in the output; do not re-run the build.