mobile

What: Apple公式のHuman Interface Guidelines（HIG）を基準に、iPhone・iPad向けiOS／iPadOSアプリのUI/UXを設計・実装・レビューし、SwiftUI／UIKitのレイアウト、ナビゲーション、コンポーネント、入力、アクセシビリティを判断する。REQUIRED when iPhone、iPad、iOS、iPadOS、SwiftUI、UIKit、HIG、App StoreのUI品質、画面設計、デザインレビュー、Dynamic Type、VoiceOver、キーボード、ポインタ、Apple Pencilを扱うとき。Differentiation: 技術アーキテクチャ、状態・データフロー、性能、テスト、Privacy Manifest、署名、TestFlight、配布はdeveloping-ios-appsを使い、UI実装では両方を併用する。Flutter独自のMaterial/CupertinoウィジェットによるクロスプラットフォームUI構築はdeveloping-flutter-appsを使う。

What: iOS/iPadOS/macOSアプリのコードベース（Info.plist、entitlements、Xcodeプロジェクト設定、ソースコード）をApp Review Guidelines（Safety/Performance/Business/Design/Legal）、In-App Purchase実装（StoreKit 2）、macOS/Mac App Store固有要件に照らして実地検査し、「必須(Blocking)/推奨/手動確認要」の3段階で判定した審査提出可否レポートを作成する。REQUIRED when 審査提出前の最終チェック、リリース可否判断、既存コードベースの審査対応状況監査を行うとき。Differentiation: App Review Guidelines本文の解説、Privacy Manifest詳細、署名・TestFlight・技術実装手順はdeveloping-ios-appsを使い、HIGに基づくUI/UX判断はapplying-apple-higを使う。本スキルは実際のプロジェクトファイルを検査するアクション型の監査に特化し、ガイドライン本文の再解説はしない。FlutterアプリがビルドするiOS/macOSのXcodeプロジェクトにも同様に適用できる。

Guides modern Dart language development, including the type system, null safety, variables, collections (List/Set/Map, Iterable, where/map/reduce), functions and functional programming (closures, higher-order functions, composition, Future/Stream), object-oriented programming (classes, constructors, inheritance, abstract classes, mixins, encapsulation, generics, enums, extension methods, operator overloading), asynchronous programming (async/await, isolates), error handling and debugging, the Dart test package, pub package management, CLI and web runtimes, and tooling (Dart SDK, DartPad, analyzer, formatter). REQUIRED when writing, reviewing, or modifying Dart code, or when pubspec.yaml or .dart files are present. For building Flutter UIs, widgets, state management, navigation, or shipping cross-platform apps, use developing-flutter-apps. For native iOS/iPadOS apps in Swift/SwiftUI, use developing-ios-apps instead.

Guides production Flutter app development with Dart targeting iOS, Android, web, and desktop from a single codebase, including project setup, the widget system (Stateless/Stateful, Material and Cupertino), layout, theming and animation, state management (setState, Provider, Riverpod, BLoC/Cubit, Redux, GetX), navigation and routing (Navigator, go_router, auto_route), networking and backends (http, dio, REST, Firebase, GraphQL), local persistence, responsive multi-platform design, architecture patterns (Clean Architecture, BLoC, MVVM), the pub.dev package ecosystem, widget and integration testing, performance optimization, and build and store release. REQUIRED when creating, implementing, modifying, testing, or shipping a Flutter app, or when pubspec.yaml lists the flutter SDK. For the Dart language itself (types, null safety, OOP, async, collections), use developing-dart. For native iOS/iPadOS apps in Swift/SwiftUI, use developing-ios-apps. For Apple HIG UI/UX decisions, use applying-apple-hig.

Guides production iPhone and iPad app development for iOS and iPadOS, including Xcode setup, SwiftUI/UIKit selection and interoperability, architecture, state and data flow, app and scene lifecycle, persistence, networking, background work, notifications, testing, performance, Privacy Manifest, Required Reason API, signing, TestFlight, App Store review, and release. REQUIRED when creating, implementing, modifying, testing, reviewing, or shipping an iOS/iPadOS app. For Apple HIG, UI/UX, navigation, layout, components, input, visual design, or accessibility decisions, use applying-apple-hig; UI implementation MUST use both skills. For codebase-level submission-readiness auditing (Info.plist/entitlements/source-code inspection with a pass/fail report), StoreKit 2 implementation-level IAP compliance, or macOS/Mac App Store-specific technical requirements (sandboxing, notarization, Hardened Runtime), use auditing-app-store-compliance instead. For cross-platform Flutter/Dart apps, use developing-flutter-apps.