engineer-sdk-setup

What problem does it solve?

Onboarding and configuring Braze SDKs involves many platform-specific steps, confusing initialization order, credential mistakes, and upgrade risks. This Skill consolidates implementation-first guidance to remove guesswork during initial setup, ensure correct identity handling, and reduce integration regressions.

Core Features & Use Cases

• Platform Coverage: Concrete setup patterns for iOS (Swift), Android, Web, React Native, Flutter, and Unity with advice on when to prefer native vs wrapper SDKs.
• Initialization & Identity: Clear rules for initializing the SDK, selecting the correct SDK API key, and calling changeUser() in the right order to preserve user identity.
• Version & Upgrade Strategy: SemVer guidance, pinning recommendations, deprecation handling, and migration patterns for MAJOR/minor upgrades.
• Customization Guidance: Decision tiers for UI customization (default, configured, custom) and warnings about manual analytics responsibilities when customizing.
• LLM & MCP Integration: Patterns to connect Context7 MCP for live documentation retrieval to generate code snippets and validate initialization signatures.
• Use Case Example: Onboarding a new mobile app team: choose native SDK, pin to a minor version, initialize in app launch, verify via test user events, and document custom event taxonomy.

Quick Start

Use this skill to get step-by-step setup guidance for initializing the Braze SDK on your target platform and verifying integration in the test workspace.