feature-flags▌

### PostHog Integration for Next.js Pages Router - Initialize PostHog using environment variables and follow the provided example project patterns for consistent implementation. - Capture analytics events directly within user-triggered event handlers rather than using useEffect hooks for state-driven logic. - Identify users during login and signup, using specific headers to maintain correlation between frontend and backend sessions.

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

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

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

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