From bd
Guides bitdrift Capture SDK setup and instrumentation in iOS, Android, and React Native apps, covering new installs plus screen tracking, network monitoring, logs, fields, and spans.
npx claudepluginhub bitdriftlabs/bd-skills --plugin bdThis skill uses the workspace's default tool permissions.
Guides integration of the bitdrift Capture SDK into mobile apps. The SDK logs everything locally on-device; the bitdrift control plane dynamically decides what to upload.
Sets up Sentry SDK for Apple platforms (iOS, macOS, tvOS, watchOS, visionOS) with error monitoring, tracing, profiling, session replay, and logging. Supports SwiftUI and UIKit.
Guides bitdrift bd CLI operations and live account data analysis for workflows, charts, sessions, issues, keys, connectors, and app health debugging.
Plans mobile app instrumentation priorities using JTBD framework. Covers tiers from crashes/user context to performance/business metrics, OTel naming, and rollout timeline.
Share bugs, ideas, or general feedback.
Guides integration of the bitdrift Capture SDK into mobile apps. The SDK logs everything locally on-device; the bitdrift control plane dynamically decides what to upload.
Use $bd-docs to fetch live API details from docs.bitdrift.io at each step. The platform reference files indicate what to look up — $bd-docs handles the mechanics of discovery and fetching.
Detect platform → Check if SDK is installed → Read platform reference → If new install: add dependency + Logger.start() → Add instrumentation categories the user needs.
Identify the target platform from the user's project:
| Signal | Platform |
|---|---|
build.gradle, build.gradle.kts, .kt, .java, AndroidManifest.xml | Android |
.xcodeproj, .xcworkspace, Package.swift, Podfile, .swift, .m/.h | iOS |
package.json with react-native, metro.config.js, App.tsx/App.js | React Native |
If the project contains files for multiple platforms (e.g., both Android and React Native in a monorepo), ask the user which target to instrument.
Check whether the bitdrift Capture SDK is already installed by searching the project for:
| Platform | SDK already present if you find… |
|---|---|
| Android | io.bitdrift:capture in build.gradle/build.gradle.kts, or import io.bitdrift.capture in source |
| iOS | capture-ios in Package.swift or BitdriftCapture in Podfile, or import Capture in source |
| React Native | @bitdrift/react-native in package.json, or import { init } from '@bitdrift/react-native' in source |
Read the platform reference file, then follow the appropriate path:
| Platform | Reference file |
|---|---|
| Android (Kotlin/Java) | references/android.md in this skill directory |
| iOS (Swift/Objective-C) | references/ios.md in this skill directory |
| React Native | references/react-native.md in this skill directory |
Each reference file has two sections:
Logger.start(). Follow this when the SDK is not yet present. Once the SDK is running, proceed to the instrumentation categories below.When asked to validate an integration, check all items and produce a report with PASS/FAIL/WARNING per check, plus concrete code fixes for failures.
| # | Check |
|---|---|
| 1 | SDK dependency present and up to date |
| 2 | Logger initialized early in app lifecycle |
| 3 | Session strategy configured |
| 4 | Network monitoring active |
| 5 | Screen tracking on every screen |
| 6 | TTI tracked |
| 7 | Crash reporter linked with session URL |
| 8 | User identity fields set after login |
| 9 | dSYM/ProGuard mapping upload configured (if applicable) |