ios-simulator-skill — Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

xcodebuild wrapper with single-line build summaries — saves huge amounts of context
Accessibility-first simulator navigation — finds elements by label, not pixel position
22 purpose-built scripts for build/test/run/simulate workflows
Auto-compressed screenshots so image tokens stay manageable
Real-time log tailing with severity filtering

Démo en direct

Aperçu en pratique

ios-simulator-skill.replay ▶ prêt

0/0

Installation

Dépôt de l’auteur · Documentation officielle des Skills Claude

Cas d'usage

Usages concrets : ios-simulator-skill

Build, run, and screenshot the current flow

👤 iOS devs using Claude Code to iterate ⏱ ~5 min beginner

Quand l'utiliser : You changed a view and want to see it live without leaving the chat.

Prérequis

Xcode + simulator installed — Standard macOS iOS dev setup

Déroulement

Ask Claude to build and run

Use ios-simulator-skill. Build MyApp scheme for iPhone 16, launch, navigate to Settings, screenshot.✓ Copié

→ Compact build summary, then the screenshot
Iterate

I tweaked the padding — rebuild and re-screenshot.✓ Copié

→ Fast turn with minimal token overhead

Résultat : Tight build-iterate-view loop in Claude Code.

Pièges

Scheme name typo causes unclear error — Skill returns a compact list of available schemes on mismatch

Combiner avec : filesystem

Drive a scripted UI flow for smoke testing

👤 iOS devs and QA ⏱ ~15 min intermediate

Quand l'utiliser : You want to verify a critical flow without writing full XCUITest scaffolding.

Déroulement

Describe the flow

Launch the app, tap 'Sign in', enter creds, tap the first row in the list, screenshot.✓ Copié

→ Claude uses accessibility labels to drive each step
Check WCAG compliance

Now run the accessibility audit on the current screen.✓ Copié

→ WCAG findings with fix suggestions

Résultat : A working smoke flow plus an a11y pass.

Pièges

Flow breaks when a label changes — Labels are more stable than coordinates, but still review after big UI refactors

Tail logs while reproducing a bug

👤 iOS devs chasing a flaky issue ⏱ ~10 min intermediate

Quand l'utiliser : A bug only repros in the simulator and you want the relevant logs.

Déroulement

Reproduce with filtered logs

Launch the app, tap through the crashing flow, tail logs filtered to error+warning.✓ Copié

→ Claude returns a trimmed log bundle and highlights the likely cause

Résultat : A targeted log excerpt and a hypothesis for the bug.

Pièges

Logs too noisy if severity filter not set — Default to error+warning; raise to info only when debugging

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

ios-simulator-skill + filesystem

Skill runs the build; filesystem reads/writes the sources

Edit SettingsView.swift, then build and screenshot.✓ Copié

ios-simulator-skill + github

Reproduce an issue from a GitHub bug report in the simulator

Read issue #42, reproduce the steps in the simulator, attach screenshot to a comment.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
xcodebuild wrapper	scheme, destination	Any build request
Simulator driver (accessibility APIs)	element label/role + action	UI automation in the simulator
Screenshot capture	none (current screen)	Visual verification
Log tailing	severity filter, duration	Debugging runtime issues
Device lifecycle	boot/shutdown/create/reset	Fresh simulator state needed
Accessibility audit	current screen	A11y review

Coût et limites

Coût d'exécution

Quota d'API: None
Tokens par appel: Very low — compact build summaries + compressed screenshots are the main design goal
Monétaire: Free — skill is local
Astuce: Keep screenshots at default compression; full-res screens eat context fast.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials in the skill. App-side secrets stay in your build config.

Sortie de données : None — everything runs on local simulators

Simulators have access to your keychain if you've configured it — be careful with credentials during automation.

Dépannage

Erreurs courantes et correctifs

'No such scheme'

Skill lists available schemes on mismatch; pick the exact name.

Vérifier : xcodebuild -list -project MyApp.xcodeproj

Accessibility label not found

Add accessibilityIdentifier to the SwiftUI view — it's more stable than the visible label.

Simulator stuck booting

Use the device-lifecycle reset command; then re-boot.

Vérifier : xcrun simctl list

Alternatives

ios-simulator-skill vs autres

Alternative	Quand l'utiliser	Compromis
Direct xcodebuild + simctl	You don't mind the token bloat from raw output	No abstraction; verbose
XcodeBuildMCP	You prefer an MCP server with structured tools	MCP route; this skill is local scripts

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills