feature-flags▌

### PostHog Go Error Tracking - Integrate PostHog by initializing exception autocapture before implementing manual error reporting. - Use environment variables for all sensitive configuration keys and host URLs to maintain security. - Upload source maps to ensure stack traces map correctly to original source code rather than minified bundles.

### PostHog Feature Flags for Next.js - Initialize PostHog globally via instrumentation-client.ts to enable hooks without wrapping components in a provider. - Evaluate flags server-side using posthog-node and pass values as props to client components to prevent hydration mismatches and flicker. - Use useFeatureFlagEnabled or useFeatureFlagPayload hooks in client components and handle loading states for asynchronous flag data.

### 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 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 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.

### 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 Python Error Tracking - Initialize the Posthog client with enable_exception_autocapture=True and use instance-based constructors instead of module-level config. - Protect user privacy by excluding PII from capture() event properties, using set() or identify_context() for person-related data instead. - Ensure reliable event delivery by registering posthog_client.shutdown with atexit and using environment variables for sensitive keys.

### 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 Android Error Tracking - Initialize PostHog in the Application class onCreate method using environment variables for keys and host URLs. - Enable exception autocapture for global coverage and use captureException for specific error boundaries and catch blocks. - Upload source maps to resolve minified stack traces and ensure activities have labels for accurate screen view tracking.