posthog▌

### Instrument Product Analytics - Detect project framework and install the appropriate PostHog SDK using the project's native package manager. - Initialize the SDK and implement event tracking for key user actions, ensuring server-side events are captured where applicable. - Use environment variables for API keys and add identify calls during authentication to maintain consistent user tracking.

### PostHog Go Logging Integration - Integrate PostHog log ingestion into Go applications using the OpenTelemetry protocol and OTLP exporters. - Use environment variables for PostHog keys and endpoints; never hardcode sensitive configuration data. - Implement structured logging with key-value properties and export logs alongside existing systems without restructuring code.

### omnibus-instrument-integration Overview - >- - Use this skill to add the PostHog SDK to an application. Use it when setting up PostHog for the first time, or reviewing PRs that need PostH - Supported frameworks: Next.js, React, React Router, Vue, Nuxt, TanStack Start, SvelteKit, Astro, Angular, Django, Flask, FastAPI, Laravel, R

### Auditing PostHog Experiments and Flags - Perform configuration audits using read_data and list_data to identify staleness, misconfigurations, and best-practice violations. - Categorize findings by severity (CRITICAL, WARNING, INFO) and provide actionable remediation steps for each identified issue. - Use inline markdown for single-entity checks and create notebook artifacts for comprehensive audits exceeding five entities.

### PostHog Feature Flags for Node.js - Integrate PostHog flags into Node.js apps using environment variables for keys and server-side evaluation to prevent UI flickering. - Implement flags alongside existing logic with minimal code changes, defaulting to boolean checks unless multivariate flags are required. - Utilize connected PostHog MCP tools to programmatically create, list, update, or delete flags directly from your development environment.

### PostHog Python Feature Flags - Use the Posthog() class constructor with enable_exception_autocapture=True and avoid hardcoding keys by using environment variables. - Implement server-side flag evaluation to prevent UI flicker and always call posthog.shutdown() or use atexit to flush events on exit. - Never include PII in capture() event properties; use set() or identify_context() to manage person properties instead.

### HogQL Query Development - Use properties.$name for event data and person.properties.$name for person attributes, utilizing bracket notation for special characters. - Include the {filters} placeholder in WHERE clauses to enable dynamic UI-based filtering and dashboard date range integration. - Optimize performance by using uniq() instead of count(distinct) and always include a timestamp-based filter to limit data scans.

### PostHog Feature Flags for Go - Integrate PostHog flags using environment variables for API keys to ensure security and avoid hardcoding credentials. - Implement server-side flag evaluation to maintain performance and prevent UI flickering in your Go applications. - Utilize available PostHog MCP tools to programmatically manage, list, and update flags directly from your development environment.

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