Flutter-SDK

Implements the Android Kotlin bridge layer for a Flutter MoEngage SDK feature. This is Step 1 of the Flutter feature pipeline — run AFTER plugin-base-feature-implementation has completed. Produces Constants.kt, MoEngage<featureNameCamel>Plugin.kt, PlatformMethodCallHandler.kt, optional EventEmitterImpl.kt, and build.gradle for a new moengage_<featureName>_android package under packages/moengage_<featureName>/. Follows the moengage_cards_android module standard exactly. On completion, asks the user whether to also run flutter-ios-bridge-implementation (Step 2). Do NOT use for iOS-only features or Dart-only changes.

Implements the Dart layer for a Flutter MoEngage SDK feature. This is Step 3 of the Flutter feature pipeline — run AFTER at least one native bridge (Android or iOS) has been implemented. Produces the platform interface package (moengage_<featureName>_platform_interface) and the main public package (moengage_<featureName>), following the moengage_cards structure exactly. Platform interface package contains: platform interface abstract class, method channel implementation, constants, payload mapper, controller (for events), instance provider, callback cache, and model/enum files from the contract protos. Main package contains: public API class and pubspec wiring both native implementations. Do NOT use before at least one native bridge exists.

Orchestrator skill for Flutter MoEngage SDK feature implementation. Runs the Android bridge, iOS bridge, and Dart interface steps in sequence. Use this when you want to do all layers in one command. If you only need one layer, invoke the focused skills directly: - Android Kotlin bridge only: flutter-android-bridge-implementation - iOS Swift bridge only: flutter-ios-bridge-implementation - Dart platform interface + public API only: flutter-dart-interface-implementation Requires: a ticket ID (MOEN-XXXXX), a contract branch in 'mobile-sdk-contracts', and at least one platform's plugin-base data. Android inputs (android_bom_version, plugin_base_bom_version, android_plugin_base_pr_url) are required for the Android bridge step — if all three are absent, the Android step is skipped. iOS inputs (ios_plugin_version, ios_plugin_base_pr_url) are required for the iOS bridge step — if both are absent, the iOS step is skipped. At least one of Android or iOS must be provided; if neither is present, the skill stops and asks.

Implements the iOS Swift bridge layer for a Flutter MoEngage SDK feature. This is Step 2 of the Flutter feature pipeline (parallel to or after flutter-android-bridge-implementation). Produces MoEngage<featureNameCamel>Plugin.swift, MoEngageFlutter<featureNameCamel>Constants.swift, optional event listener .swift, optional util .swift, podspec, and pubspec.yaml for a new moengage_<featureName>_ios package under packages/moengage_<featureName>/. Follows the moengage_cards_ios module standard exactly. On completion, asks the user whether to also run flutter-dart-implementation. Do NOT use for Android-only features or Dart-only changes.

Updates the iOS plugin dependency version for one or more Flutter MoEngage SDK packages. For each specified package, updates two files: the podspec (s.dependency version) and Package.swift (exact: version). Also prepends a CHANGELOG entry to the iOS package CHANGELOG and to the parent (main) package CHANGELOG. Use this when a new ios-plugin-base or feature-specific iOS plugin version is released.