ios-debugger-agent は何をしますか？
XcodeBuildMCPを使用して、起動済みシミュレーター上でiOSプロジェクトをビルド、実行、起動、デバッグします。iOSアプリの実行、シミュレーターUIの操作、画面状態の検査、ログ/コンソール出力の取得、XcodeBuildMCPツールを使ったランタイム動作の診断を求められたときに起動します。
XcodeBuildMCPを使用して、起動済みシミュレーター上でiOSプロジェクトをビルド、実行、起動、デバッグします。iOSアプリの実行、シミュレーターUIの操作、画面状態の検査、ログ/コンソール出力の取得、XcodeBuildMCPツールを使ったランタイム動作の診断を求められたときに起動します。
このスキルは、XcodeBuildMCPツール群を活用してiOSアプリケーションの開発ワークフローを効率化するためのエージェントスキルです。起動済みのiOSシミュレーター上でプロジェクトをビルドし、アプリを起動・実行し、ランタイムのデバッグを支援します。具体的には、アプリのUI状態の確認、コンソールログやシステムログの取得、シミュレーター上でのユーザー操作のシミュレーションなど、開発者が手動で行う煩雑な作業をエージェントが代行できます。Xcodeのビルドシステムと直接連携するため、複雑な設定は不要で、プロジェクトの設定に従って正確に動作します。また、CI/CDパイプラインとの統合や、AIエージェント（Claude Code, Cursor, Codexなど）との組み合わせにも適しており、iOS開発の生産性を大幅に向上させます。
npx skills add https://github.com/dimillian/skills/tree/main/skills/ios-debugger-agentXcodeBuildMCPを使用して、起動済みシミュレーター上でiOSプロジェクトをビルド、実行、起動、デバッグします。iOSアプリの実行、シミュレーターUIの操作、画面状態の検査、ログ/コンソール出力の取得、XcodeBuildMCPツールを使ったランタイム動作の診断を求められたときに起動します。
This repo contains 7 individual skills — each has its own dedicated page.
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project. Use when you need a from-scratch macOS app layout, SwiftPM targets/resources, a custom .app bundle assembly script, or signing/notarization/appcast steps outside Xcode.
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file. Concrete actions include adding Sendable conformance, applying @MainActor annotations, resolving actor isolation warnings, fixing data race diagnostics, and migrating completion handlers to async/await.
Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.
Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
Best practices and example-driven guidance for building SwiftUI views and components, including navigation hierarchies, custom view modifiers, and responsive layouts with stacks and grids. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens with VStack/HStack, managing @State or @Binding, building declarative iOS interfaces, or needing component-specific patterns and examples.
Refactor and review SwiftUI view files with strong defaults for small dedicated subviews, MV-over-MVVM data flow, stable view trees, explicit dependency injection, and correct Observation usage. Use when cleaning up a SwiftUI view, splitting long bodies, removing inline actions or side effects, reducing computed `some View` helpers, or standardizing `@Observable` and view model initialization patterns.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".