feature-flags▌

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

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

### PostHog Logging for Next.js - Integrate PostHog log ingestion into Next.js applications using the OpenTelemetry protocol and OTLP exporters. - Utilize environment variables for all PostHog keys and endpoints to ensure security and avoid hardcoding sensitive data. - Implement structured logging with key-value properties and initialize via instrumentation.ts for optimal framework compatibility.

### PostHog Integration for Static Astro - Initialize PostHog by creating a reusable posthog.astro component and importing it into your site's main layout. - Use the is:inline directive on script tags and prefix client-side environment variables with PUBLIC_ to ensure proper functionality. - Identify users during authentication events and maintain session correlation by passing distinct IDs via custom request headers.

### feature-flags-dotnet Overview - PostHog feature flags for .NET applications - This skill helps you add PostHog feature flags to .NET applications. - `references/dotnet.md` - .net feature flags installation - docs

### PostHog Flask Integration - Initialize the Posthog client globally in create_app() using the instance-based constructor with enable_exception_autocapture=True. - Use posthog_client.set() to manage person properties and ensure atexit.register() is used to flush events before application shutdown. - Protect user privacy by never including PII in capture() event properties; use identify() patterns for user-specific data instead.

### PostHog Log Integration for Datadog - Configure OTLP exporters to send logs to PostHog's ingest endpoint using the OpenTelemetry protocol. - Use environment variables for all PostHog keys and endpoints to ensure security and avoid hardcoding sensitive credentials. - Implement structured logging with key-value properties instead of plain text to improve searchability and data analysis.

### PostHog Integration for Angular - Create a singleton PosthogService using inject() to wrap the SDK and manage analytics across standalone components. - Store PostHog credentials in environment.ts files and avoid hardcoding keys directly into the application source code. - Identify users during authentication and pass session headers to maintain data correlation between frontend and backend services.

### PostHog LLM Analytics Integration - Integrate PostHog analytics into any LLM application using provider-specific guides or the manual capture fallback for custom setups. - Capture essential metrics including input/output tokens, model names, latency, and costs while ensuring PII is never sent in events. - Use the instance-based Posthog() constructor, enable exception autocapture, and call shutdown() to ensure all events are flushed.