moengage

Review Android SDK documentation from the perspective of a junior Android developer performing an integration for the first time. Covers integration correctness, code validity, navigation flow, deprecated APIs, and writing standards. Use when asked to review any page under developer-guide/android-sdk/.

Write, edit, and maintain MoEngage documentation. Use for collaborative drafting, autonomous writing, or improving existing docs. Defaults to collaborative mode where the human makes final decisions. Adapted from Mintlify's doc-author skill for the MoEngage docs repo.

Comprehensive reference for the Mintlify platform as used by the MoEngage docs site. Use when creating pages, configuring docs.json, adding components, setting up navigation, or working with API references. Routes to detailed reference files for all components and configuration options.

Review React Native SDK documentation for writing standards, technical accuracy, RN-specific usability, and Mintlify component correctness. Use when asked to review any page under developer-guide/react-native-sdk/.

Add new pages to the MoEngage docs.json navigation structure. Updates navigation groups based on the correct tab (Home, User Guide, Developer Guide, API Guide) and the user journey. Use when the user asks to add a page to navigation, update docs.json, add to nav, or include a new page in the sidebar.

Review MoEngage Android or iOS SDK changelog files from the perspective of a junior developer who reads them to decide whether to upgrade and what action to take. Covers upgrade decision clarity, content quality, formatting consistency, versioning accuracy, and link correctness for entries post-January 2025.

Read and navigate external documentation efficiently. Invoke when the task requires checking how a specific function, endpoint, or configuration option works; when the user references an API, SDK, library, or third-party tool by name; when any docs URL or documentation site is mentioned; or when implementing something that depends on an external service or package. Adapted from Mintlify's doc-reader skill.

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.

Implements the Android Kotlin bridge layer for a React-Native MoEngage SDK feature. This is Step 2a of the React-Native feature pipeline — run AFTER plugin-base-feature-implementation has completed. Produces the BridgeHandler, arch bridges (new/old), Package, EventEmitterImpl, PayloadGenerator, Constants, and build.gradle for a new sdk/<featureName> module in the React-Native repo, following the Cards module standard. On completion, asks the user whether to also run react-native-ts-implementation (Step 2b). Do NOT use for iOS-only features or JS-only changes.

Orchestrator skill for React-Native feature implementation. Runs the Android bridge, iOS bridge, and TypeScript steps. 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: react-native-android-bridge-implementation - iOS ObjC bridge only: react-native-ios-bridge-implementation - TypeScript layer only: react-native-ts-implementation Requires: a ticket ID (MOEN-XXXXX), a contract branch in 'mobile-sdk-contracts', and a target Android BOM version. iOS inputs (ios_plugin_version, ios_plugin_base_pr_url) are optional — if both are absent, the iOS bridge step is skipped (feature is Android-only or iOS will be done later). Run AFTER plugin-base-feature-implementation. Do NOT use for JS-only changes or before plugin-base changes exist.

Implements the iOS bridge layer for a React-Native MoEngage SDK feature. This is Step 2b of the React-Native feature pipeline (parallel to or after react-native-android-bridge-implementation). Produces the Bridge .h/.mm, Handler .h/.m, Constants .h/.m, optional Util .h/.m, and podspec for a new sdk/<featureName> module in the React-Native repo, following the Cards module standard. On completion, asks the user whether to also run react-native-ts-implementation. Do NOT use for Android-only features or JS-only changes.

Implements the TypeScript layer for a React-Native MoEngage SDK feature. Run AFTER at least one native bridge (Android or iOS) has been implemented. Produces the TurboModule NativeSpec, model classes, enums, PayloadBuilder, PayloadParser, JsonToModelMapper, Handler, PublicApi, index, package.json, and podspec. Can be used for iOS-only features (no Android bridge required).

Create a minor version PR for iOS-PluginBase based on a new native SDK API and SDK contract. Scaffolds the feature branch, implements the bridge method, updates constants, CHANGELOG, and version — then generates the branch locally via a CI script.

Updates the version in package.json and prepends a new entry in CHANGELOG.md. Determines bump type (major/minor/patch) from the new version automatically. Can be used standalone or called from other skills like minor-version-pr.

Create a minor version PR for apple-plugin-inbox based on a new native SDK API and SDK contract. Reads contracts remotely, implements the bridge method, updates CHANGELOG and version — then creates a PR.

Updates the version in package.json and prepends a new entry in CHANGELOG.md. Determines bump type (major/minor/patch) from the new version automatically. Can be used standalone or called from other skills like native-feature-implementation.

Create a minor version PR for apple-plugin-cards based on a new native SDK API and SDK contract. Reads contracts remotely, implements the bridge method, updates CHANGELOG and version — then creates a PR.

Updates the version in package.json and prepends a new entry in CHANGELOG.md. Determines bump type (major/minor/patch) from the new version automatically. Can be used standalone or called from other skills like minor-version-pr.

Create a minor version PR for apple-plugin-geofence based on a new native SDK API and SDK contract. Reads contracts remotely, implements the bridge method, updates CHANGELOG and version — then creates a PR.

Updates the version in package.json and prepends a new entry in CHANGELOG.md. Determines bump type (major/minor/patch) from the new version automatically. Can be used standalone or called from other skills like minor-version-pr.