posthog▌

### PostHog Ruby Integration - Install the posthog-ruby gem and initialize the client using environment variables for API keys and host configuration. - Use client.capture and client.identify with hash arguments, but use positional arguments for client.capture_exception. - Ensure client.shutdown is called before script exit to prevent event loss, ideally within an ensure block for proper cleanup.

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

### PostHog Integration for Nuxt 3.6 - Follow the four-step setup workflow to initialize PostHog analytics within your Nuxt 3.0 to 3.6 application. - Use environment variables for all PostHog keys and maintain consistency by following the provided example project patterns. - Identify users during authentication events and use specific headers to correlate client-side sessions with backend requests.

### PostHog React Native Integration - Install posthog-react-native and react-native-svg, then wrap your app with PostHogProvider inside the NavigationContainer. - Use react-native-config to securely load POSTHOG_PROJECT_TOKEN and POSTHOG_HOST from environment variables at build time. - Identify users during login and signup, using custom headers to maintain session correlation between frontend and backend.

### PostHog Integration for React and Vite - Follow the four-step workflow to initialize, configure, and finalize PostHog analytics within your React application. - Use environment variables for API keys and implement analytics capture directly within event handlers rather than useEffect hooks. - Identify users during authentication and maintain session correlation by passing distinct IDs via headers in API requests.

### PostHog Integration for React Router v7 - Implement PostHog analytics using the declarative pattern by following the four-step setup workflow and referencing the example project. - Use environment variables for API keys and trigger analytics capture directly within event handlers rather than inside useEffect hooks. - Identify users during authentication and maintain session correlation by passing distinct IDs via headers for backend-integrated flows.

### PostHog PHP Feature Flags - Install the posthog/posthog-php SDK and initialize it once using PostHog::init() with environment variables for API keys. - Implement server-side flag checks to prevent UI flickering, defaulting to boolean flags unless multivariate logic is required. - Use PostHog MCP tools to manage flags directly and ensure all SDK methods utilize associative arrays for distinct IDs and properties.

### PostHog Integration for Nuxt 4 - Follow the four-step setup workflow to integrate PostHog analytics into your Nuxt 4 application. - Use environment variables for all PostHog keys and follow the provided example project patterns for implementation. - Identify users during authentication and use specific headers to maintain session correlation between frontend and backend.

### omnibus-instrument-error-tracking Overview - >- - Use this skill to add PostHog error tracking that captures and monitors exceptions in your application. Use it after implementing features o - Supported platforms: React, Next.js, Web (JavaScript), Node.js, Python, Ruby, Ruby on Rails, Go, Angular, Svelte, Nuxt, React Native, Flutte

### PostHog LLM Analytics Instrumentation - Detect the LLM stack and existing PostHog setup to determine if SDK installation or specific provider-based tracing is required. - Instrument LLM calls to capture essential metrics including token counts, latency, model names, and costs for every generation. - Use environment variables for API keys and associate generations with user IDs while keeping code modifications minimal and targeted.