posthog▌

### 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 JavaScript Web Integration - Initialize posthog-js in client-side browser environments only, ensuring posthog.init() is called before any other SDK methods. - Use posthog.identify() for PII like emails and names, while keeping posthog.capture() event properties free of sensitive user data. - Follow the four-step integration workflow and use environment variables for keys to maintain security and implementation consistency.

### PostHog Web Error Tracking - Initialize posthog-js before other methods and enable exception autocapture to monitor browser errors automatically. - Upload source maps to ensure stack traces are readable and use captureException() within catch blocks for manual error reporting. - Protect user privacy by excluding PII from capture() event properties, using identify() for user-specific data instead.

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

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