ios-debugger-agent
Debug the current iOS project on a booted simulator with XcodeBuildMCP.
Best use case
ios-debugger-agent is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Debug the current iOS project on a booted simulator with XcodeBuildMCP.
Teams using ios-debugger-agent should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ios-debugger-agent/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ios-debugger-agent Compares
| Feature / Agent | ios-debugger-agent | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Debug the current iOS project on a booted simulator with XcodeBuildMCP.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# iOS Debugger Agent ## Overview Use XcodeBuildMCP to build and run the current project scheme on a booted iOS simulator, interact with the UI, and capture logs. Prefer the MCP tools for simulator control, logs, and view inspection. ## When to Use - When the user asks to run, debug, or inspect an iOS app on a simulator. - When you need simulator UI interaction, screenshots, or runtime logs via XcodeBuildMCP. ## Core Workflow Follow this sequence unless the user asks for a narrower action. ### 1) Discover the booted simulator - Call `mcp__XcodeBuildMCP__list_sims` and select the simulator with state `Booted`. - If none are booted, ask the user to boot one (do not boot automatically unless asked). ### 2) Set session defaults - Call `mcp__XcodeBuildMCP__session-set-defaults` with: - `projectPath` or `workspacePath` (whichever the repo uses) - `scheme` for the current app - `simulatorId` from the booted device - Optional: `configuration: "Debug"`, `useLatestOS: true` ### 3) Build + run (when requested) - Call `mcp__XcodeBuildMCP__build_run_sim`. - **If the build fails**, check the error output and retry (optionally with `preferXcodebuild: true`) or escalate to the user before attempting any UI interaction. - **After a successful build**, verify the app launched by calling `mcp__XcodeBuildMCP__describe_ui` or `mcp__XcodeBuildMCP__screenshot` before proceeding to UI interaction. - If the app is already built and only launch is requested, use `mcp__XcodeBuildMCP__launch_app_sim`. - If bundle id is unknown: 1) `mcp__XcodeBuildMCP__get_sim_app_path` 2) `mcp__XcodeBuildMCP__get_app_bundle_id` ## UI Interaction & Debugging Use these when asked to inspect or interact with the running app. - **Describe UI**: `mcp__XcodeBuildMCP__describe_ui` before tapping or swiping. - **Tap**: `mcp__XcodeBuildMCP__tap` (prefer `id` or `label`; use coordinates only if needed). - **Type**: `mcp__XcodeBuildMCP__type_text` after focusing a field. - **Gestures**: `mcp__XcodeBuildMCP__gesture` for common scrolls and edge swipes. - **Screenshot**: `mcp__XcodeBuildMCP__screenshot` for visual confirmation. ## Logs & Console Output - Start logs: `mcp__XcodeBuildMCP__start_sim_log_cap` with the app bundle id. - Stop logs: `mcp__XcodeBuildMCP__stop_sim_log_cap` and summarize important lines. - For console output, set `captureConsole: true` and relaunch if required. ## Troubleshooting - If build fails, ask whether to retry with `preferXcodebuild: true`. - If the wrong app launches, confirm the scheme and bundle id. - If UI elements are not hittable, re-run `describe_ui` after layout changes. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
deploy-to-vercel
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
ckm:ui-styling
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
ckm:design
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.
ckm:design-system
Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.
ckm:brand
Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.