Omnibus Instrument Product Analytics
PostHogOfficialCreated by PostHog
- Skill
- Tool integration
- Data and AI
- MIT
- Low risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured, step-by-step procedure for integrating PostHog product analytics into a wide variety of web, mobile, and backend frameworks. It handles the full lifecycle of the integration, from detecting the project's technology stack and installing the necessary SDKs to implementing event tracking, user identification, and error monitoring. The skill emphasizes non-intrusive changes, ensuring that new analytics code is added alongside existing logic without disrupting the project's architecture.
What it does
- Detects the project framework and language to determine the correct PostHog SDK.
- Installs the required PostHog SDK package automatically.
- Initializes the PostHog instance according to framework-specific best practices.
- Implements targeted event tracking for key user actions and business logic.
- Configures user identification flows for login and signup events.
- Sets up environment variables for secure API key and host management.
When to use it
- After implementing new features that require tracking for user engagement analysis.
- When reviewing pull requests to ensure critical user behaviors are being captured.
- When setting up product analytics for a new project from scratch.
- When migrating or adding analytics to an existing application.
Advantages
- Supports a broad range of modern frontend, backend, and mobile frameworks.
- Ensures consistent event naming and property capture across the codebase.
- Maintains architectural integrity by requiring minimal, targeted code additions.
- Automates the tedious aspects of SDK initialization and environment configuration.
Usage examples
- “Add PostHog analytics to my Next.js project.”
- The agent will detect the Next.js environment, install the PostHog SDK, initialize it in the appropriate root file, and guide you through adding capture calls to key user flows.
- “I need to track user signups in my Django application using PostHog.”
- The agent will identify the Django setup, configure the PostHog Python SDK, and implement identify calls within your authentication logic.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/posthog/omnibus-instrument-product-analytics/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip omnibus-instrument-product-analytics.zip -d .agents/skills
Documentation by PostHog
Add PostHog product analytics events
Use this skill to add product analytics events (capture calls) that track meaningful user actions in new or changed code. Use it after implementing features or reviewing PRs to ensure key user behaviors are captured. If PostHog is not yet installed, this skill also covers initial SDK setup. Supports any framework or language.
Supported frameworks: Next.js, React Router, Nuxt, Vue, TanStack Start, SvelteKit, Astro, Angular, Django, Flask, FastAPI, Laravel, Ruby on Rails, Android, iOS, React Native, Expo, and more.
Instructions
Follow these steps IN ORDER:
STEP 1: Analyze the codebase and detect the platform.
Look for dependency files (package.json, requirements.txt, Gemfile, composer.json, go.mod, etc.) to determine the framework and language.
Look for lockfiles (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb) to determine the package manager.
Check for existing PostHog setup. If PostHog is already installed and initialized, skip to STEP 5.
STEP 2: Research integration. (Skip if PostHog is already set up.) 2.1. Find the reference file below that matches the detected framework — it is the source of truth for SDK initialization, provider setup, and event capture patterns. Read it now. 2.2. If no reference matches, fall back to your general knowledge and web search. Use posthog.com/docs as the primary search source.
STEP 3: Install the PostHog SDK. (Skip if PostHog is already set up.)
Add the PostHog SDK package for the detected platform. Do not manually edit package.json — use the package manager's install command.
Always install packages as a background task. Don't await completion; proceed with other work immediately after starting the installation.
STEP 4: Initialize PostHog. (Skip if PostHog is already set up.)
Follow the framework reference for where and how to initialize. This varies significantly by framework (e.g., instrumentation-client.ts for Next.js 15.3+, AppConfig.ready() for Django, create_app() for Flask).
STEP 5: Plan event tracking.
From the project's file list, select between 10 and 15 files that might have interesting business value for event tracking, especially conversion and churn events.
Also look for files related to login that could be used for identifying users, along with error handling.
Find any existing
posthog.capture()code. Make note of event name formatting. Don't duplicate existing events; supplement them.Track actions only, not pageviews (those can be captured automatically). Exceptions can be made for "viewed"-type events at the top of a conversion funnel.
Server-side events are REQUIRED if the project includes any instrumentable server-side code (API routes, server actions, webhook handlers, payment/checkout completion, authentication endpoints).
STEP 6: Implement event capture.
For each planned event, add
posthog.capture()calls with useful properties.If a file already has existing integration code for other tools or services, don't overwrite or remove that code. Place PostHog code below it.
Do not alter the fundamental architecture of existing files. Make additions minimal and targeted.
You must read a file immediately before attempting to write it.
STEP 7: Identify users.
Add PostHog
identify()calls on the client side during login and signup events. Use the contents of login and signup forms to identify users on submit.If both frontend and backend exist, pass the client-side session and distinct ID using
X-POSTHOG-DISTINCT-IDandX-POSTHOG-SESSION-IDheaders to the server-side code. On the server side, make sure events have a matching distinct ID.
STEP 8: Add error tracking.
Add PostHog exception capture error tracking to relevant files, particularly around critical user flows and API boundaries.
STEP 9: Set up environment variables.
If an env-file-tools MCP server is connected, use check_env_keys to see which keys already exist, then use set_env_values to create or update the PostHog API key and host.
Reference these environment variables in code instead of hardcoding them.
STEP 10: Verify and clean up.
Check the project for errors. Look for type checking or build scripts in package.json.
Ensure any components created were actually used.
Run any linter or prettier-like scripts found in the package.json.
Reference files
references/EXAMPLE-next-app-router.md- next-app-router example project codereferences/EXAMPLE-next-pages-router.md- next-pages-router example project codereferences/EXAMPLE-react-react-router-6.md- react-react-router-6 example project codereferences/EXAMPLE-react-react-router-7-framework.md- react-react-router-7-framework example project codereferences/EXAMPLE-react-react-router-7-data.md- react-react-router-7-data example project codereferences/EXAMPLE-react-react-router-7-declarative.md- react-react-router-7-declarative example project codereferences/EXAMPLE-nuxt-3.6.md- nuxt-3.6 example project codereferences/EXAMPLE-nuxt-4.md- nuxt-4 example project codereferences/EXAMPLE-vue-3.md- vue-3 example project codereferences/EXAMPLE-react-tanstack-router-file-based.md- react-tanstack-router-file-based example project codereferences/EXAMPLE-react-tanstack-router-code-based.md- react-tanstack-router-code-based example project codereferences/EXAMPLE-tanstack-start.md- tanstack-start example project codereferences/EXAMPLE-sveltekit.md- sveltekit example project codereferences/EXAMPLE-astro-static.md- astro-static example project codereferences/EXAMPLE-astro-view-transitions.md- astro-view-transitions example project codereferences/EXAMPLE-astro-ssr.md- astro-ssr example project codereferences/EXAMPLE-astro-hybrid.md- astro-hybrid example project codereferences/EXAMPLE-angular.md- angular example project codereferences/EXAMPLE-django.md- django example project codereferences/EXAMPLE-flask.md- flask example project codereferences/EXAMPLE-fastapi.md- fastapi example project codereferences/EXAMPLE-python.md- python example project codereferences/EXAMPLE-laravel.md- laravel example project codereferences/EXAMPLE-ruby-on-rails.md- ruby-on-rails example project codereferences/EXAMPLE-ruby.md- ruby example project codereferences/EXAMPLE-android.md- android example project codereferences/EXAMPLE-swift.md- swift example project codereferences/EXAMPLE-react-native.md- react-native example project codereferences/EXAMPLE-expo.md- expo example project codereferences/next-js.md- Next.js - docsreferences/react-router-v6.md- React router v6 - docsreferences/react-router-v7-framework-mode.md- React router v7 framework mode (remix v3) - docsreferences/react-router-v7-data-mode.md- React router v7 data mode - docsreferences/react-router-v7-declarative-mode.md- React router v7 declarative mode - docsreferences/nuxt-js-3-6.md- Nuxt.js (v3.0 to v3.6) - docsreferences/nuxt-js.md- Nuxt.js - docsreferences/vue-js.md- Vue.js - docsreferences/tanstack-start.md- Tanstack start - docsreferences/svelte.md- Svelte - docsreferences/astro.md- Astro - docsreferences/angular.md- Angular - docsreferences/django.md- Django - docsreferences/flask.md- Flask - docsreferences/python.md- Python - docsreferences/posthog-python.md- PostHog python SDKreferences/laravel.md- Laravel - docsreferences/ruby-on-rails.md- Ruby on rails - docsreferences/ruby.md- Ruby - docsreferences/android.md- Android - docsreferences/ios.md- Ios - docsreferences/react-native.md- React native - docsreferences/identify-users.md- Identify users - docs
Each framework reference contains SDK-specific installation, initialization, and usage patterns. Find the one matching the user's stack.
Key principles
Environment variables: Always use environment variables for PostHog keys. Never hardcode them.
Minimal changes: Add PostHog code alongside existing integrations. Don't replace or restructure existing code.
Match the docs: Follow the framework reference's initialization and capture patterns exactly.
Files
- ATTRIBUTION.mdAdded by AutoGineer966 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md8.5 KiB
- references/EXAMPLE-android.md49.7 KiB
- references/EXAMPLE-angular.md23.4 KiB
- references/EXAMPLE-astro-hybrid.md26.8 KiB
- references/EXAMPLE-astro-ssr.md26.7 KiB
- references/EXAMPLE-astro-static.md19.4 KiB
- references/EXAMPLE-astro-view-transitions.md23.1 KiB
- references/EXAMPLE-django.md30.0 KiB
- references/EXAMPLE-expo.md35.5 KiB
- references/EXAMPLE-fastapi.md40.9 KiB
- references/EXAMPLE-flask.md32.0 KiB
- references/EXAMPLE-javascript-node.md9.0 KiB
- references/EXAMPLE-javascript-web.md11.7 KiB
- references/EXAMPLE-laravel.md59.5 KiB
- references/EXAMPLE-next-app-router.md17.3 KiB
- references/EXAMPLE-next-pages-router.md18.9 KiB
- references/EXAMPLE-nuxt-3.6.md22.1 KiB
- references/EXAMPLE-nuxt-4.md28.7 KiB
- references/EXAMPLE-python.md11.6 KiB
- references/EXAMPLE-react-native.md46.4 KiB
- references/EXAMPLE-react-react-router-6.md13.5 KiB
- references/EXAMPLE-react-react-router-7-data.md20.1 KiB
- references/EXAMPLE-react-react-router-7-declarative.md15.0 KiB
- references/EXAMPLE-react-react-router-7-framework.md32.2 KiB
- references/EXAMPLE-react-tanstack-router-code-based.md19.2 KiB
- references/EXAMPLE-react-tanstack-router-file-based.md18.0 KiB
- references/EXAMPLE-react-vite.md12.4 KiB
- references/EXAMPLE-ruby-on-rails.md37.6 KiB
- references/EXAMPLE-ruby.md10.3 KiB
- references/EXAMPLE-sveltekit.md18.4 KiB
- references/EXAMPLE-swift.md18.6 KiB
- references/EXAMPLE-tanstack-start.md28.4 KiB
- references/EXAMPLE-vue-3.md17.9 KiB
- references/android.md21.7 KiB
- references/angular.md12.5 KiB
- references/astro.md8.3 KiB
- references/django.md6.7 KiB
- references/flask.md2.9 KiB
- references/identify-users.md8.1 KiB
- references/ios.md5.4 KiB
- references/js.md12.3 KiB
- references/laravel.md2.1 KiB
- references/next-js.md12.5 KiB
- references/node.md28.8 KiB
- references/nuxt-js-3-6.md6.6 KiB
- references/nuxt-js.md7.2 KiB
- references/posthog-js.md42.3 KiB
- references/posthog-node.md23.4 KiB
- references/posthog-python.md31.3 KiB
- references/python.md31.1 KiB
- references/react-native.md43.8 KiB
- references/react-router-v6.md11.6 KiB
- references/react-router-v7-data-mode.md11.4 KiB
- references/react-router-v7-declarative-mode.md11.6 KiB
- references/react-router-v7-framework-mode.md14.9 KiB
- references/react.md18.5 KiB
- references/ruby-on-rails.md10.6 KiB
- references/ruby.md18.9 KiB
- references/svelte.md7.2 KiB
- references/tanstack-start.md5.1 KiB
- references/vue-js.md9.1 KiB
references/EXAMPLE-swift.md
PostHog swift Example Project
Repository: https://github.com/PostHog/context-mill Path: basics/swift
README.md
PostHog Swift (iOS/macOS) example
This is a SwiftUI example demonstrating PostHog integration with product analytics, error tracking, and user identification. The app targets both iOS and macOS using NavigationSplitView.
Features
Product analytics: Track user events and behaviors
Error tracking: Capture and track errors
User identification: Associate events with authenticated users
Multi-platform: Runs on iOS, iPadOS, macOS, and visionOS
Getting started
1. Add the PostHog dependency
The Xcode project already includes the PostHog iOS SDK via Swift Package Manager. When you open the project, Xcode will resolve the package automatically.
To add it manually to a new project: File > Add Package Dependencies > enter https://github.com/PostHog/posthog-ios.
2. Configure environment variables
Set your PostHog project token and host as environment variables in the Xcode scheme:
In Xcode, go to Product > Scheme > Edit Scheme…
Select Run in the sidebar
Go to the Arguments tab
Under Environment Variables, add:
| Variable | Value |
|---|---|
POSTHOG_PROJECT_TOKEN | Your PostHog project token |
POSTHOG_HOST | https://us.i.posthog.com |
Get your PostHog project token from your PostHog project settings.
The app reads these via ProcessInfo.processInfo.environment and will crash with a clear message if they're missing.
3. Build and run
Open BurritoConsiderationClient.xcodeproj in Xcode and run on an iOS Simulator or macOS.
Project structure
BurritoConsiderationClient/
├── BurritoConsiderationClientApp.swift # App entry point with PostHog initialization
├── ContentView.swift # NavigationSplitView with sidebar routing
├── UserState.swift # @Observable user state with PostHog identify
├── LoginView.swift # Login form
├── DashboardView.swift # Welcome screen with dashboard_viewed tracking
├── BurritoView.swift # Burrito consideration with event capture
├── ProfileView.swift # Profile with journey progress and error trigger
└── Assets.xcassets/ # Asset catalogKey integration points
PostHog initialization (BurritoConsiderationClientApp.swift)
import PostHog
guard let POSTHOG_PROJECT_TOKEN = ProcessInfo.processInfo.environment["POSTHOG_PROJECT_TOKEN"],
let POSTHOG_HOST = ProcessInfo.processInfo.environment["POSTHOG_HOST"] else {
fatalError("Set POSTHOG_PROJECT_TOKEN and POSTHOG_HOST in the Xcode scheme environment variables.")
}
let config = PostHogConfig(apiKey: POSTHOG_PROJECT_TOKEN, host: POSTHOG_HOST)
config.captureApplicationLifecycleEvents = true
PostHogSDK.shared.setup(config)User identification (UserState.swift)
PostHogSDK.shared.identify(username, userProperties: [
"username": username,
])Screen view tracking (DashboardView.swift, ProfileView.swift)
.onAppear {
PostHogSDK.shared.capture("dashboard_viewed", properties: [
"username": userState.username ?? "unknown",
])
}Event tracking (BurritoView.swift)
PostHogSDK.shared.capture("burrito_considered", properties: [
"total_considerations": count,
"username": username,
])Error tracking (ProfileView.swift)
PostHogSDK.shared.capture("test_error_triggered", properties: [
"error_type": "test",
"error_message": error.localizedDescription,
])User logout (UserState.swift)
PostHogSDK.shared.capture("user_logged_out")
PostHogSDK.shared.reset()Learn more
BurritoConsiderationClient.xcodeproj/project.xcworkspace/contents.xcworkspacedata
<?xml version="1.0" encoding="UTF-8"?>
<Workspace
version = "1.0">
<FileRef
location = "self:">
</FileRef>
</Workspace>
BurritoConsiderationClient.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved
{
"originHash" : "a2fc303e4b16c93c972ef2ddc4042cf91a9400e5d1639bc9740a80c0336cdd4e",
"pins" : [
{
"identity" : "posthog-ios",
"kind" : "remoteSourceControl",
"location" : "https://github.com/PostHog/posthog-ios",
"state" : {
"revision" : "1783865d79a1cabc472cf2d56a1fe3f797417b52",
"version" : "3.40.0"
}
}
],
"version" : 3
}
BurritoConsiderationClient.xcodeproj/xcshareddata/xcschemes/BurritoConsiderationClient.xcscheme
<?xml version="1.0" encoding="UTF-8"?>
<Scheme
LastUpgradeVersion = "2630"
version = "1.7">
<BuildAction
parallelizeBuildables = "YES"
buildImplicitDependencies = "YES"
buildArchitectures = "Automatic">
<BuildActionEntries>
<BuildActionEntry
buildForTesting = "YES"
buildForRunning = "YES"
buildForProfiling = "YES"
buildForArchiving = "YES"
buildForAnalyzing = "YES">
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "1F6BD9732F3520A100189B0B"
BuildableName = "BurritoConsiderationClient.app"
BlueprintName = "BurritoConsiderationClient"
ReferencedContainer = "container:BurritoConsiderationClient.xcodeproj">
</BuildableReference>
</BuildActionEntry>
</BuildActionEntries>
</BuildAction>
<TestAction
buildConfiguration = "Debug"
selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB"
selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB"
shouldUseLaunchSchemeArgsEnv = "YES"
shouldAutocreateTestPlan = "YES">
</TestAction>
<LaunchAction
buildConfiguration = "Debug"
selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB"
selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB"
launchStyle = "0"
useCustomWorkingDirectory = "NO"
ignoresPersistentStateOnLaunch = "NO"
debugDocumentVersioning = "YES"
debugServiceExtension = "internal"
allowLocationSimulation = "YES">
<BuildableProductRunnable
runnableDebuggingMode = "0">
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "1F6BD9732F3520A100189B0B"
BuildableName = "BurritoConsiderationClient.app"
BlueprintName = "BurritoConsiderationClient"
ReferencedContainer = "container:BurritoConsiderationClient.xcodeproj">
</BuildableReference>
</BuildableProductRunnable>
<EnvironmentVariables>
<EnvironmentVariable
key = "POSTHOG_PROJECT_TOKEN"
value = "phc_jE9kXU0depRekiuabVROlxxkIXn95NqsNO3qB4qNKtl"
isEnabled = "YES">
</EnvironmentVariable>
<EnvironmentVariable
key = "POSTHOG_HOST"
value = "https://us.i.posthog.com"
isEnabled = "YES">
</EnvironmentVariable>
</EnvironmentVariables>
</LaunchAction>
<ProfileAction
buildConfiguration = "Release"
shouldUseLaunchSchemeArgsEnv = "YES"
savedToolIdentifier = ""
useCustomWorkingDirectory = "NO"
debugDocumentVersioning = "YES">
<BuildableProductRunnable
runnableDebuggingMode = "0">
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "1F6BD9732F3520A100189B0B"
BuildableName = "BurritoConsiderationClient.app"
BlueprintName = "BurritoConsiderationClient"
ReferencedContainer = "container:BurritoConsiderationClient.xcodeproj">
</BuildableReference>
</BuildableProductRunnable>
</ProfileAction>
<AnalyzeAction
buildConfiguration = "Debug">
</AnalyzeAction>
<ArchiveAction
buildConfiguration = "Release"
revealArchiveInOrganizer = "YES">
</ArchiveAction>
</Scheme>
BurritoConsiderationClient/BurritoConsiderationClientApp.swift
//
// BurritoConsiderationClientApp.swift
// BurritoConsiderationClient
//
// Created by Danilo Campos on 2/5/26.
//
import SwiftUI
import PostHog
enum PostHogEnv: String {
case apiKey = "POSTHOG_PROJECT_TOKEN"
case host = "POSTHOG_HOST"
var value: String {
guard let value = ProcessInfo.processInfo.environment[rawValue] else {
fatalError("Set \(rawValue) in the Xcode scheme environment variables.")
}
return value
}
}
@main
struct BurritoConsiderationClientApp: App {
@State private var userState = UserState()
init() {
let config = PostHogConfig(apiKey: PostHogEnv.apiKey.value, host: PostHogEnv.host.value)
config.captureApplicationLifecycleEvents = true
config.debug = true
PostHogSDK.shared.setup(config)
}
var body: some Scene {
WindowGroup {
ContentView()
.environment(userState)
}
}
}
BurritoConsiderationClient/BurritoView.swift
//
// BurritoView.swift
// BurritoConsiderationClient
//
import SwiftUI
import PostHog
struct BurritoView: View {
@Environment(UserState.self) private var userState
@State private var showConfirmation = false
var body: some View {
VStack(spacing: 24) {
Text("Take a moment to truly consider the potential of burritos.")
.foregroundStyle(.secondary)
.multilineTextAlignment(.center)
Text("🌯")
.font(.system(size: 80))
Button("I Have Considered the Burrito Potential") {
userState.burritoConsiderations += 1
// PostHog: Capture burrito consideration event
PostHogSDK.shared.capture("burrito_considered", properties: [
"total_considerations": userState.burritoConsiderations,
"username": userState.username ?? "unknown",
])
showConfirmation = true
Task {
try? await Task.sleep(for: .seconds(2))
showConfirmation = false
}
}
.buttonStyle(.borderedProminent)
.controlSize(.large)
if showConfirmation {
Text("Thank you for your consideration! Count: \(userState.burritoConsiderations)")
.foregroundStyle(.green)
.transition(.opacity)
}
Text("Total considerations: \(userState.burritoConsiderations)")
.font(.title2)
.padding(.top)
}
.padding()
.animation(.default, value: showConfirmation)
.navigationTitle("Burrito Consideration Zone")
}
}
BurritoConsiderationClient/ContentView.swift
//
// ContentView.swift
// BurritoConsiderationClient
//
// Created by Danilo Campos on 2/5/26.
//
import SwiftUI
enum Screen: CaseIterable, Identifiable {
case dashboard, burrito, profile
var id: Self { self }
var title: String {
switch self {
case .dashboard: "Home"
case .burrito: "Burrito"
case .profile: "Profile"
}
}
var icon: String {
switch self {
case .dashboard: "house"
case .burrito: "fork.knife"
case .profile: "person.circle"
}
}
}
struct ContentView: View {
@Environment(UserState.self) private var userState
@State private var selectedScreen: Screen? = .dashboard
var body: some View {
if userState.isLoggedIn {
NavigationSplitView {
List(Screen.allCases, selection: $selectedScreen) { screen in
Label(screen.title, systemImage: screen.icon)
}
.navigationTitle("Menu")
} detail: {
if let selectedScreen {
switch selectedScreen {
case .dashboard:
DashboardView()
case .burrito:
BurritoView()
case .profile:
ProfileView()
}
} else {
Text("Select an item from the sidebar")
.foregroundStyle(.secondary)
}
}
} else {
NavigationStack {
LoginView()
}
}
}
}
BurritoConsiderationClient/DashboardView.swift
//
// DashboardView.swift
// BurritoConsiderationClient
//
import SwiftUI
import PostHog
struct DashboardView: View {
@Environment(UserState.self) private var userState
var body: some View {
VStack(spacing: 20) {
Text("Welcome back, \(userState.username ?? "")!")
.font(.largeTitle)
.padding(.top, 40)
Text("You are now logged in. Feel free to explore:")
.foregroundStyle(.secondary)
VStack(alignment: .leading, spacing: 12) {
Label("Consider the potential of burritos", systemImage: "fork.knife")
Label("View your profile and statistics", systemImage: "person.circle")
}
.padding()
Spacer()
}
.padding()
.navigationTitle("Home")
.onAppear {
// PostHog: Track dashboard view
PostHogSDK.shared.capture("dashboard_viewed", properties: [
"username": userState.username ?? "unknown",
])
}
}
}
BurritoConsiderationClient/LoginView.swift
//
// LoginView.swift
// BurritoConsiderationClient
//
import SwiftUI
struct LoginView: View {
@Environment(UserState.self) private var userState
@State private var username = ""
@State private var password = ""
@State private var showError = false
var body: some View {
Form {
Section("Login") {
TextField("Username", text: $username)
#if os(iOS)
.textInputAutocapitalization(.never)
#endif
.autocorrectionDisabled()
SecureField("Password", text: $password)
}
Section {
Button("Log In") {
if !userState.login(username: username, password: password) {
showError = true
}
}
.disabled(username.isEmpty || password.isEmpty)
}
}
.formStyle(.grouped)
.navigationTitle("Burrito Consideration")
.alert("Login Failed", isPresented: $showError) {
Button("OK", role: .cancel) { }
} message: {
Text("Please enter a valid username and password.")
}
}
}
BurritoConsiderationClient/ProfileView.swift
//
// ProfileView.swift
// BurritoConsiderationClient
//
import SwiftUI
import PostHog
struct ProfileView: View {
@Environment(UserState.self) private var userState
private var journeyMessage: String {
switch userState.burritoConsiderations {
case 0:
"You haven't considered any burritos yet. Visit the Burrito Consideration page to start!"
case 1:
"You've considered the burrito potential once. Keep going!"
case 2...4:
"You're getting the hang of burrito consideration!"
case 5...9:
"You're becoming a burrito consideration expert!"
default:
"You are a true burrito consideration master!"
}
}
var body: some View {
Form {
Section("Your Information") {
LabeledContent("Username", value: userState.username ?? "—")
LabeledContent("Burrito Considerations", value: "\(userState.burritoConsiderations)")
}
Section("Your Burrito Journey") {
Text(journeyMessage)
}
Section("Diagnostics") {
Button("Trigger Test Error") {
let error = NSError(
domain: "com.posthog.BurritoConsiderationClient",
code: 42,
userInfo: [NSLocalizedDescriptionKey: "Test error triggered by user"]
)
// PostHog: Capture exception for error tracking
PostHogSDK.shared.capture("test_error_triggered", properties: [
"error_type": "test",
"error_message": error.localizedDescription,
"username": userState.username ?? "unknown",
])
}
}
Section {
Button("Log Out", role: .destructive) {
userState.logout()
}
}
}
.formStyle(.grouped)
.navigationTitle("Profile")
.onAppear {
// PostHog: Track profile view
PostHogSDK.shared.capture("profile_viewed", properties: [
"username": userState.username ?? "unknown",
])
}
}
}
BurritoConsiderationClient/UserState.swift
//
// UserState.swift
// BurritoConsiderationClient
//
import Foundation
import PostHog
@Observable
class UserState {
var username: String?
var burritoConsiderations: Int = 0
var isLoggedIn: Bool {
username != nil
}
func login(username: String, password: String) -> Bool {
// In a real app, validate credentials against a backend
guard !username.isEmpty, !password.isEmpty else {
return false
}
self.username = username
self.burritoConsiderations = 0
// PostHog: Identify user on login
PostHogSDK.shared.identify(username, userProperties: [
"username": username,
])
// PostHog: Capture login event
PostHogSDK.shared.capture("user_logged_in", properties: [
"username": username,
])
return true
}
func logout() {
// PostHog: Capture logout event before reset
PostHogSDK.shared.capture("user_logged_out")
PostHogSDK.shared.reset()
username = nil
burritoConsiderations = 0
}
}
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs an API key, Needs Python, Needs Node.js
Security
What our scanner noticed· Low risk
- Instructions that use the network
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- PostHog
- Publisher
- PostHog (Official)
- Source
- PostHog/skills · skills/posthog/integration/skills/all · commit a5d30e7
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- PostHog/skills
AutoGineer is not affiliated with or endorsed by PostHog or PostHog.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download omnibus-instrument-product-analytics.zip