with one click
debug
WHEN users express issues with app behavior, visual appearance, or functionality in the iOS simulator collaborate on fixes with a structured feedback loop.
Menu
WHEN users express issues with app behavior, visual appearance, or functionality in the iOS simulator collaborate on fixes with a structured feedback loop.
WHEN scraping iOS/macOS App Store data (apps, reviews, ratings, search); NOT for installing or testing apps; retrieves structured JSON data using iTunes/App Store APIs with curl and jq formatting
Comprehensive guide for implementing on-device AI models on iOS using Foundation Models and MLX Swift frameworks. Use WHEN building iOS apps with (1) Local LLM inference, (2) Vision Language Models (VLMs), (3) Text embeddings, (4) Image generation, (5) Tool/function calling, (6) Multi-turn conversations, (7) Custom model integration, or (8) Structured generation.
WHEN building ChatGPT apps using the OpenAI Apps SDK and MCP; create conversational, composable experiences with proper UX, UI, state management, and server patterns.
WHEN building SwiftUI views, managing state, setting up shared services, or making architectural decisions; NOT for UIKit or legacy patterns; provides pure SwiftUI data flow without ViewModels using @State, @Binding, @Observable, and @Environment.
WHEN building design systems or component libraries with Tailwind CSS; covers design tokens, CVA patterns and dark mode.
WHEN building React components/pages/apps; enforces scalable architecture, state management, API layer, performance patterns.
| name | debug |
| description | WHEN users express issues with app behavior, visual appearance, or functionality in the iOS simulator collaborate on fixes with a structured feedback loop. |
Use XcodeBuildMCP and ios-simulator MCPs to diagnose issues, capture app state, and collaborate with users on fixes. Always confirm before making changes.
Capture current state — Use ios-simulator to capture screenshots and understand the current visual state of the app. Use XcodeBuildMCP to read build logs and runtime errors.
Gather diagnostic information — Collect relevant information:
Analyze the problem — Review the captured information:
Propose changes clearly — Describe intended fixes with specifics:
Confirm before implementing — Use AskUserQuestion to get explicit approval. Never modify code without confirmation.
Verify with comparison — After changes:
Use these XcodeBuildMCP tools for building and analyzing:
build — Build the Xcode project/workspaceget-build-logs — Retrieve build logs to diagnose compilation errorsget-runtime-logs — Get runtime logs from the running appclean — Clean build artifacts before rebuildingtest — Run unit tests to verify fixesUse these ios-simulator tools for app interaction and state capture:
launch-app — Launch the app in the simulatortake-screenshot — Capture the current simulator screentap — Tap at specific coordinates on the screenswipe — Perform swipe gesturesenter-text — Type text into focused text fieldsget-device-info — Get simulator device informationinstall-app — Install the app on the simulatoruninstall-app — Uninstall the app from the simulatorWhen implementing fixes, load these skills for guidance:
app:swiftui-architecture — SwiftUI patterns, state management, and architectural guidanceapp:swift-testing — Testing patterns and best practicesAfter implementing changes: