feature-flags▌

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

### 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 Feature Flags for Flutter - Integrate PostHog flags into Flutter apps using environment variables for keys and avoiding hardcoded credentials. - Implement boolean flag checks alongside existing logic to maintain code structure and minimize unnecessary refactoring. - Prioritize server-side flag evaluation to prevent UI flickering and utilize MCP tools for direct flag management.

### PostHog Error Tracking for React - Initialize PostHog with exception autocapture enabled and use environment variables for all sensitive configuration keys. - Upload source maps to ensure stack traces are readable and use captureException in error boundaries for non-propagating errors. - Integrate error tracking alongside existing logic without restructuring or replacing current error handling patterns.

### PostHog Error Tracking for Ruby on Rails - Install the posthog-rails gem and use the initializer to enable automatic exception capture and ActiveJob instrumentation. - Use environment variables for API keys and host URLs, ensuring sensitive configuration is never hardcoded in the codebase. - Utilize class-level PostHog methods for event capture and identify calls, avoiding manual client instantiation within Rails.

### PostHog Flutter Error Tracking - Integrate PostHog by enabling exception autocapture during SDK initialization before implementing manual error reporting. - Use environment variables for API keys and host URLs to maintain security and avoid hardcoding sensitive configuration data. - Upload source maps to ensure minified stack traces are resolved into readable code for effective debugging and issue monitoring.

### PostHog Angular Error Tracking - Implement a singleton PosthogService using inject() to wrap the SDK and manage initialization within standalone components. - Enable exception autocapture during SDK initialization and use captureException() for errors caught at specific boundaries. - Secure credentials via environment files and upload source maps to ensure stack traces resolve to original source code.

### 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 Next.js - Initialize PostHog in instrumentation-client.ts and enable exception autocapture before implementing manual error tracking. - Upload source maps to ensure stack traces resolve to original source code rather than minified bundles. - Use captureException() within error boundaries and catch blocks to record errors that do not reach the global handler.