back
loading skill details...
Install and initialize the correct LaunchDarkly SDK during onboarding by running nested skills in order: detect, plan, apply. Parent onboarding Step 6 is first…
LaunchDarkly SDK Install (onboarding) Installs and initializes the right LaunchDarkly SDK for the user’s project by following three nested skills in order. Do not skip ahead to feature flags here—the parent LaunchDarkly onboarding continues with Step 6: First feature flag using Create first feature flag. Prerequisites Project context from parent Step 1: Explore the Project (reuse it; only re-run deep detection if something is unclear) SDK key / client-side ID / mobile key: Needed when you reach Apply code changes (env wiring). Do not ask the user for these during detect or plan solely because you opened this skill—follow parent onboarding: account status is inferred via MCP OAuth (Step 4) or surfaced at D7 in apply; key material is collected at apply (see parent Prerequisites). Key types (summary) SDK Type Variable (logical) Source in LaunchDarkly Server-side LAUNCHDARKLY_SDK_KEY Environments → SDK key Client-side Client-side ID (bundler-prefixed env names) Environments → Client-side ID Mobile LAUNCHDARKLY_MOBILE_KEY Environments → Mobile key Never hardcode keys. Full env rules, consent, and bundler tables: Apply code changes Step 2.
don't have the plugin yet? install it then click "run inline in claude" again.