feature-flags-ios — Claude Code skill: what it does, how to install
feature-flags-ios adds PostHog feature flags to iOS apps, manages SPM dependencies cleanly, and enforces environment variable handling in Xcode.
MIT 112 installs ★ 80 updated 2026-10-24
npx skills add PostHog/skills --skill feature-flags-ios -a claude-codeWhat feature-flags-ios does
This skill guides coding assistants when integrating PostHog feature flags into Swift projects. It prioritizes boolean flags by default and keeps existing business logic intact rather than refactoring surrounding functions. For configuration, it structures a PostHogEnv enum fetching POSTHOG_PROJECT_TOKEN and POSTHOG_HOST via ProcessInfo. Omitting these environment variables from the Xcode scheme causes an intentional runtime fatalError.
The skill also handles project configuration details. When editing project.pbxproj, it creates distinct PBXBuildFile, XCSwiftPackageProductDependency, and XCRemoteSwiftPackageReference entries with fresh release versions from posthog-ios. If a PostHog MCP server is active, the assistant manages flags through MCP tools instead of directing you to the web dashboard. For App Sandbox targets on macOS, it enables ENABLE_OUTGOING_NETWORK_CONNECTIONS so client events can reach the server.
What it helps with
- integrate posthog-ios SPM dependencies directly into project.pbxproj
- read PostHog tokens from Xcode scheme variables instead of hardcoding
- evaluate boolean feature flags alongside existing Swift UI code
- enable outgoing network connections in macOS App Sandbox targets
Example prompts for the agent
- Add a boolean feature flag check for the new checkout view
- Configure the PostHogEnv enum and read credentials from Xcode scheme variables
- Check available PostHog flags via the connected MCP server
How to install feature-flags-ios
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-ios -a claude-code2Manually: put the files in place
~/.claude/skills/feature-flags-ios/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/feature-flags-ios/
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-ios -a codex2Manually: put the files in place
.agents/skills/feature-flags-ios/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-ios -a cursor2Manually: put the files in place
.cursor/skills/feature-flags-ios/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/skills skills/posthog/all/skills/feature-flags-ios2Manually: put the files in place
.github/skills/feature-flags-ios/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-ios -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/skills --path skills/posthog/all/skills/feature-flags-iosManually: put the files in place
.devin/skills/feature-flags-ios/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-ios -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about feature-flags-ios
How do I install feature-flags-ios in Claude Code?
Run npx skills add PostHog/skills --skill feature-flags-ios -a claude-code in your terminal.
What does feature-flags-ios do?
It provides architectural rules for adding PostHog flags into iOS projects, managing SPM package references in Xcode, and querying PostHog MCP tools.
How does the skill handle API keys?
It generates a PostHogEnv enum pulling POSTHOG_PROJECT_TOKEN and POSTHOG_HOST directly from ProcessInfo environment variables, avoiding plain text secrets in source code.
Source text
SKILL.md · MIT
--- name: feature-flags-ios description: PostHog feature flags for iOS applications metadata: author: PostHog version: 1.9.4 --- # PostHog feature flags for iOS This skill helps you add PostHog feature flags to iOS applications. ## Reference files - `references/ios.md` - Ios feature flags installation - docs - `references/adding-feature-flag-code.md` - Adding feature flag code - docs - `references/best-practices.md` - Feature flag best practices - docs Consult the documentation for API details and framework-specific patterns. ## Key principles - **Environment variables**: Always use environment variables for PostHog keys. Never hardcode them. - **Minimal changes**: Add feature flag code alongside existing logic. Don't replace or restructure existing code. - **Boolean flags first**: Default to boolean flag checks unless the user specifically asks for multivariate flags. - **Server-side when possible**: Prefer server-side flag evaluation to avoid UI flicker. ## PostHog MCP tools Check if a PostHog MCP server is connected. If available, look for tools related to feature flag management (creating, listing, updating, deleting flags). Use these tools to manage flags directly in PostHog rather than requiring the user to do it manually in the dashboard. ## Framework guidelines - Read configuration from environment variables via a `PostHogEnv` enum with a `value` computed property that calls `ProcessInfo.processInfo.environment[rawValue]` and `fatalError`s if missing — cases should be `projectToken = "POSTHOG_PROJECT_TOKEN"` and `host = "POSTHOG_HOST"`, set in the Xcode scheme's Run environment variables - When adding SPM dependencies to project.pbxproj, create three distinct objects with unique UUIDs — a `PBXBuildFile` (with `productRef`), an `XCSwiftPackageProductDependency` (with `package` and `productName`), and an `XCRemoteSwiftPackageReference` (with `repositoryURL` and `requirement`). The build file goes in the Frameworks phase `files`, the product dependency goes in the target's `packageProductDependencies`, and the package reference goes in the project's `packageReferences`. - Check the latest release version of posthog-ios at `https://github.com/PostHog/posthog-ios/releases` before setting the `minimumVersion` in the SPM package reference — do not hardcode a stale version - If the project uses App Sandbox (macOS), add `ENABLE_OUTGOING_NETWORK_CONNECTIONS = YES` to the target's build settings so PostHog can reach its servers — do NOT disable the sandbox entirely
© PostHog · MIT · PostHog/skills