feature-flags▌

### PostHog Error Tracking for Svelte - Initialize PostHog with exception autocapture enabled and use environment variables for all sensitive configuration keys. - Upload source maps to ensure stack traces resolve to original source code rather than minified production bundles. - Set paths.relative to false in svelte.config.js to ensure session replay compatibility with SvelteKit server-side rendering.

### PostHog Feature Flags in Rust - Integrate PostHog flags into Rust applications using environment variables for secure API key management. - Implement server-side flag evaluation to ensure consistent user experiences and prevent UI flickering. - Utilize available PostHog MCP tools to programmatically manage, list, and update feature flags directly from your development environment.

### PostHog Error Tracking for Hono - Integrate PostHog error tracking into Hono apps using environment variables for keys and host URLs to ensure security. - Enable exception autocapture in the SDK initialization and use captureException() for errors at specific boundary catch blocks. - Upload source maps to resolve stack traces to original source code and maintain existing error handling structures without replacement.

### PostHog iOS Feature Flags - Securely manage PostHog keys using environment variables and a dedicated enum to prevent hardcoding sensitive configuration data. - Implement SPM dependencies by creating distinct PBXBuildFile, XCSwiftPackageProductDependency, and XCRemoteSwiftPackageReference objects. - Prioritize server-side flag evaluation to prevent UI flickering and enable outgoing network connections for sandboxed applications.

### PostHog React Native Error Tracking - Install posthog-react-native and react-native-svg, using environment variables for project tokens and host URLs. - Enable exception autocapture in the SDK initialization and use captureException() within error boundaries for manual reporting. - Upload source maps to ensure stack traces resolve to original source code and wrap the app with PostHogProvider for full integration.

### PostHog Ruby Error Tracking - Install the posthog-ruby gem and initialize the client using environment variables for API keys and host URLs to ensure security. - Enable exception autocapture for global coverage and use capture_exception in rescue blocks for errors that do not propagate. - Always call client.shutdown in an ensure block for CLI or script applications to prevent event loss before the process exits.

### PostHog Feature Flags for Elixir - Integrate PostHog flags into Elixir apps using environment variables for keys and server-side evaluation to prevent UI flickering. - Implement feature flags alongside existing logic without restructuring code, defaulting to boolean checks for simplicity. - Utilize available PostHog MCP tools to manage flag lifecycles directly from the development environment instead of the dashboard.

### PostHog Error Tracking for Nuxt - Integrate PostHog error tracking into Nuxt applications using environment variables for secure configuration of keys and host URLs. - Enable exception autocapture in the SDK initialization and use captureException for manual error handling at specific boundaries. - Upload source maps to ensure stack traces resolve to original source code rather than minified production bundles.

### feature-flags-android Overview - PostHog feature flags for Android applications - This skill helps you add PostHog feature flags to Android applications. - `references/android.md` - Android feature flags installation - docs

### PostHog React Feature Flags - Use useFeatureFlagEnabled or useFeatureFlagPayload hooks to manage flags while handling loading states and external synchronization. - Secure PostHog keys using environment variables and prefer server-side flag evaluation to prevent UI flickering during rendering. - Avoid using useEffect for state management or event handling; reserve it strictly for synchronizing with external systems.