[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756XZPWJSRTQQPEKSP8M25V":3,"skill-same:01M756XZPWJSRTQQPEKSP8M25V":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M756XZPWJSRTQQPEKSP8M25V","posthog-multi-env-setup",null,"Configure PostHog across development, staging, and production environments.\nUse when setting up multi-environment event capture, managing separate PostHog\nprojects per environment, or configuring feature flags and recordings by env.\nTrigger with phrases like \"posthog environments\", \"posthog staging\",\n\"posthog dev prod\", \"posthog environment setup\", \"posthog project per env\".","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fposthog-multi-env-setup\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: posthog-multi-env-setup\ndescription: |\n  Configure PostHog across development, staging, and production environments.\n  Use when setting up multi-environment event capture, managing separate PostHog\n  projects per environment, or configuring feature flags and recordings by env.\n  Trigger with phrases like \"posthog environments\", \"posthog staging\",\n  \"posthog dev prod\", \"posthog environment setup\", \"posthog project per env\".\nallowed-tools: Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# PostHog Multi-Environment Setup\n\n## Overview\nSeparate PostHog projects per environment is strongly recommended over using one project with event filtering. Each environment gets its own Project API Key (starts with `phc_`) and Project ID.\n\n## Prerequisites\n- PostHog Cloud account or self-hosted instance\n- Separate PostHog projects for dev, staging, and production\n- Project API keys (`phc_...`) and Project IDs for each environment\n- Personal API key for admin operations (optional)\n\n## Environment Strategy\n\n| Environment | PostHog Project | Session Recording | Autocapture | Key Source |\n|-------------|----------------|-------------------|-------------|------------|\n| Development | `myapp-dev` | Disabled | Enabled | `.env.local` |\n| Staging | `myapp-staging` | Disabled | Enabled | CI\u002FCD secrets |\n| Production | `myapp-production` | Enabled (sampled) | Enabled | Secret manager |\n\n## Instructions\n\n### Step 1: Create Separate PostHog Projects\n```\nPostHog Cloud: app.posthog.com > New Project\n- \"myapp-development\" -> copy phc_... API key\n- \"myapp-staging\"     -> copy phc_... API key\n- \"myapp-production\"  -> copy phc_... API key\n```\n\n### Step 2: Environment-Specific PostHog Configuration\n```typescript\n\u002F\u002F config\u002Fposthog.ts\ntype Env = \"development\" | \"staging\" | \"production\";\n\ninterface PostHogConfig {\n  apiKey: string;                   \u002F\u002F phc_... project key\n  host: string;                     \u002F\u002F app.posthog.com or self-hosted URL\n  sessionRecording: boolean;\n  samplingRate: number;             \u002F\u002F 0-1 for session recording\n}\n\nconst configs: Record\u003CEnv, PostHogConfig> = {\n  development: {\n    apiKey: process.env.NEXT_PUBLIC_POSTHOG_KEY_DEV!,\n    host: \"https:\u002F\u002Fapp.posthog.com\",\n    sessionRecording: false,         \u002F\u002F never record in dev\n    samplingRate: 0,\n  },\n  staging: {\n    apiKey: process.env.NEXT_PUBLIC_POSTHOG_KEY_STAGING!,\n    host: \"https:\u002F\u002Fapp.posthog.com\",\n    sessionRecording: false,         \u002F\u002F no recordings in staging\n    samplingRate: 0,\n  },\n  production: {\n    apiKey: process.env.NEXT_PUBLIC_POSTHOG_KEY_PROD!,\n    host: \"https:\u002F\u002Fapp.posthog.com\",\n    sessionRecording: true,\n    samplingRate: 0.25,              \u002F\u002F record 25% of sessions\n  },\n};\n\nexport function getPostHogConfig(): PostHogConfig {\n  const env = (process.env.NODE_ENV || \"development\") as Env;\n  const config = configs[env] || configs.development;\n  if (!config.apiKey) {\n    console.warn(`PostHog API key not set for ${env} -- analytics disabled`);\n  }\n  return config;\n}\n```\n\n### Step 3: Next.js PostHog Provider\n```typescript\n\u002F\u002F app\u002Fproviders.tsx\n\"use client\";\nimport posthog from \"posthog-js\";\nimport { PostHogProvider } from \"posthog-js\u002Freact\";\nimport { useEffect } from \"react\";\nimport { getPostHogConfig } from \"..\u002Fconfig\u002Fposthog\";\n\nexport function PHProvider({ children }: { children: React.ReactNode }) {\n  const config = getPostHogConfig();\n\n  useEffect(() => {\n    if (!config.apiKey) return;\n\n    posthog.init(config.apiKey, {\n      api_host: config.host,\n      disable_session_recording: !config.sessionRecording,\n      session_recording: config.sessionRecording\n        ? { sampleRate: config.samplingRate }\n        : undefined,\n      capture_pageview: false,     \u002F\u002F use usePathname in Next.js App Router\n      loaded: (ph) => {\n        if (process.env.NODE_ENV === \"development\") {\n          ph.debug();\n        }\n      },\n    });\n  }, []);\n\n  return \u003CPostHogProvider client={posthog}>{children}\u003C\u002FPostHogProvider>;\n}\n```\n\n### Step 4: Server-Side Node.js Setup\n```typescript\n\u002F\u002F lib\u002Fposthog-server.ts\nimport { PostHog } from \"posthog-node\";\n\nlet _client: PostHog | null = null;\n\nexport function getPostHogServer(): PostHog {\n  if (_client) return _client;\n\n  const config = getPostHogConfig();\n  if (!config.apiKey) return { capture: () => {} } as any; \u002F\u002F no-op if unconfigured\n\n  _client = new PostHog(config.apiKey, {\n    host: config.host,\n    flushAt: 20,\n    flushInterval: 10000,  # 10000: 10 seconds in ms\n  });\n\n  return _client;\n}\n```\n\n### Step 5: Environment Variable Setup\n```bash\n# .env.local\nNEXT_PUBLIC_POSTHOG_KEY_DEV=phc_dev_abc123\nPOSTHOG_PROJECT_ID_DEV=12345  # port 12345 - example\u002Ftest\n\n# .env.staging\nNEXT_PUBLIC_POSTHOG_KEY_STAGING=phc_staging_def456\nPOSTHOG_PROJECT_ID_STAGING=12346  # 12346 = configured value\n\n# Production (GitHub Actions \u002F cloud secret manager)\n# NEXT_PUBLIC_POSTHOG_KEY_PROD=phc_prod_xyz789\n# POSTHOG_PROJECT_ID_PROD=12347\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Dev events in prod project | Same API key across envs | Use separate projects per env |\n| No events captured | `apiKey` not set in env vars | Check `NEXT_PUBLIC_` prefix for client-side keys |\n| Session recordings in staging | `sessionRecording: true` in staging | Set `sessionRecording: false` for non-prod |\n| `401` from server-side | Wrong key type | Project key (`phc_...`) is for capture; personal key for admin API |\n\n## Examples\n\n### Verify Environment Routing\n```typescript\nimport { getPostHogConfig } from \".\u002Fconfig\u002Fposthog\";\n\nconst cfg = getPostHogConfig();\nconsole.log(`PostHog key: ${cfg.apiKey.slice(0, 10)}...`);\nconsole.log(`Session recording: ${cfg.sessionRecording ? \"ON\" : \"OFF\"}`);\n```\n\n### Feature Flag Rollout Per Environment\n```typescript\n\u002F\u002F Staging project: 100% rollout for QA\n\u002F\u002F Production project: 10% initial rollout\nconst flagValue = await posthogServer.getFeatureFlag(\"new-checkout\", userId);\n```\n\n## Resources\n- [PostHog Multi-Environment Guide](https:\u002F\u002Fposthog.com\u002Fdocs\u002Ffeature-flags\u002Fmulti-environment-feature-flags)\n- [PostHog Next.js Integration](https:\u002F\u002Fposthog.com\u002Fdocs\u002Flibraries\u002Fnext-js)\n- [PostHog Node.js SDK](https:\u002F\u002Fposthog.com\u002Fdocs\u002Flibraries\u002Fnode)\n\n## Next Steps\nFor webhook setup, see `posthog-webhooks-events`.\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale","# PostHog Multi-Environment Setup\n\n## Overview\nSeparate PostHog projects per environment is strongly recommended over using one project with event filtering. Each environment gets its own Project API Key (starts with `phc_`) and Project ID.\n\n## Prerequisites\n- PostHog Cloud account or self-hosted instance\n- Separate PostHog projects for dev, staging, and production\n- Project API keys (`phc_...`) and Project IDs for each environment\n- Personal API key for admin operations (optional)\n\n## Environment Strategy\n\n| Environment | PostHog Project | Session Recording | Autocapture | Key Source |\n|-------------|----------------|-------------------|-------------|------------|\n| Development | `myapp-dev` | Disabled | Enabled | `.env.local` |\n| Staging | `myapp-staging` | Disabled | Enabled | CI\u002FCD secrets |\n| Production | `myapp-production` | Enabled (sampled) | Enabled | Secret manager |\n\n## Instructions\n\n### Step 1: Create Separate PostHog Projects\n```\nPostHog Cloud: app.posthog.com > New Project\n- \"myapp-development\" -> copy phc_... API key\n- \"myapp-staging\"     -> copy phc_... API key\n- \"myapp-production\"  -> copy phc_... API key\n```\n\n### Step 2: Environment-Specific PostHog Configuration\n```typescript\n\u002F\u002F config\u002Fposthog.ts\ntype Env = \"development\" | \"staging\" | \"production\";\n\ninterface PostHogConfig {\n  apiKey: string;                   \u002F\u002F phc_... project key\n  host: string;                     \u002F\u002F app.posthog.com or self-hosted URL\n  sessionRecording: boolean;\n  samplingRate: number;             \u002F\u002F 0-1 for session recording\n}\n\nconst configs: Record\u003CEnv, PostHogConfig> = {\n  development: {\n    apiKey: process.env.NEXT_PUBLIC_POSTHOG_KEY_DEV!,\n    host: \"https:\u002F\u002Fapp.posthog.com\",\n    sessionRecording: false,         \u002F\u002F never record in dev\n    samplingRate: 0,\n  },\n  staging: {\n    apiKey: process.env.NEXT_PUBLIC_POSTHOG_KEY_STAGING!,\n    host: \"https:\u002F\u002Fapp.posthog.com\",\n    sessionRecording: false,         \u002F\u002F no recordings in staging\n    samplingRate: 0,\n  },\n  production: {\n    apiKey: process.env.NEXT_PUBLIC_POSTHOG_KEY_PROD!,\n    host: \"https:\u002F\u002Fapp.posthog.com\",\n    sessionRecording: true,\n    samplingRate: 0.25,              \u002F\u002F record 25% of sessions\n  },\n};\n\nexport function getPostHogConfig(): PostHogConfig {\n  const env = (process.env.NODE_ENV || \"development\") as Env;\n  const config = configs[env] || configs.development;\n  if (!config.apiKey) {\n    console.warn(`PostHog API key not set for ${env} -- analytics disabled`);\n  }\n  return config;\n}\n```\n\n### Step 3: Next.js PostHog Provider\n```typescript\n\u002F\u002F app\u002Fproviders.tsx\n\"use client\";\nimport posthog from \"posthog-js\";\nimport { PostHogProvider } from \"posthog-js\u002Freact\";\nimport { useEffect } from \"react\";\nimport { getPostHogConfig } from \"..\u002Fconfig\u002Fposthog\";\n\nexport function PHProvider({ children }: { children: React.ReactNode }) {\n  const config = getPostHogConfig();\n\n  useEffect(() => {\n    if (!config.apiKey) return;\n\n    posthog.init(config.apiKey, {\n      api_host: config.host,\n      disable_session_recording: !config.sessionRecording,\n      session_recording: config.sessionRecording\n        ? { sampleRate: config.samplingRate }\n        : undefined,\n      capture_pageview: false,     \u002F\u002F use usePathname in Next.js App Router\n      loaded: (ph) => {\n        if (process.env.NODE_ENV === \"development\") {\n          ph.debug();\n        }\n      },\n    });\n  }, []);\n\n  return \u003CPostHogProvider client={posthog}>{children}\u003C\u002FPostHogProvider>;\n}\n```\n\n### Step 4: Server-Side Node.js Setup\n```typescript\n\u002F\u002F lib\u002Fposthog-server.ts\nimport { PostHog } from \"posthog-node\";\n\nlet _client: PostHog | null = null;\n\nexport function getPostHogServer(): PostHog {\n  if (_client) return _client;\n\n  const config = getPostHogConfig();\n  if (!config.apiKey) return { capture: () => {} } as any; \u002F\u002F no-op if unconfigured\n\n  _client = new PostHog(config.apiKey, {\n    host: config.host,\n    flushAt: 20,\n    flushInterval: 10000,  # 10000: 10 seconds in ms\n  });\n\n  return _client;\n}\n```\n\n### Step 5: Environment Variable Setup\n```bash\n# .env.local\nNEXT_PUBLIC_POSTHOG_KEY_DEV=phc_dev_abc123\nPOSTHOG_PROJECT_ID_DEV=12345  # port 12345 - example\u002Ftest\n\n# .env.staging\nNEXT_PUBLIC_POSTHOG_KEY_STAGING=phc_staging_def456\nPOSTHOG_PROJECT_ID_STAGING=12346  # 12346 = configured value\n\n# Production (GitHub Actions \u002F cloud secret manager)\n# NEXT_PUBLIC_POSTHOG_KEY_PROD=phc_prod_xyz789\n# POSTHOG_PROJECT_ID_PROD=12347\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Dev events in prod project | Same API key across envs | Use separate projects per env |\n| No events captured | `apiKey` not set in env vars | Check `NEXT_PUBLIC_` prefix for client-side keys |\n| Session recordings in staging | `sessionRecording: true` in staging | Set `sessionRecording: false` for non-prod |\n| `401` from server-side | Wrong key type | Project key (`phc_...`) is for capture; personal key for admin API |\n\n## Examples\n\n### Verify Environment Routing\n```typescript\nimport { getPostHogConfig } from \".\u002Fconfig\u002Fposthog\";\n\nconst cfg = getPostHogConfig();\nconsole.log(`PostHog key: ${cfg.apiKey.slice(0, 10)}...`);\nconsole.log(`Session recording: ${cfg.sessionRecording ? \"ON\" : \"OFF\"}`);\n```\n\n### Feature Flag Rollout Per Environment\n```typescript\n\u002F\u002F Staging project: 100% rollout for QA\n\u002F\u002F Production project: 10% initial rollout\nconst flagValue = await posthogServer.getFeatureFlag(\"new-checkout\", userId);\n```\n\n## Resources\n- [PostHog Multi-Environment Guide](https:\u002F\u002Fposthog.com\u002Fdocs\u002Ffeature-flags\u002Fmulti-environment-feature-flags)\n- [PostHog Next.js Integration](https:\u002F\u002Fposthog.com\u002Fdocs\u002Flibraries\u002Fnext-js)\n- [PostHog Node.js SDK](https:\u002F\u002Fposthog.com\u002Fdocs\u002Flibraries\u002Fnode)\n\n## Next Steps\nFor webhook setup, see `posthog-webhooks-events`.\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Configure PostHog across development, staging, and production environments.\nUse when setting up multi-environment event capture, managing separate PostHog\nprojects per environment, or configuring feature flags and recordings by env.\nTrigger with phrases like \"posthog environments\", \"posthog staging\",\n\"posthog dev prod\", \"posthog environment setup\", \"posthog project per env\".\n","Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*)","claude-code, codex, openclaw","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill posthog-multi-env-setup",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill posthog-multi-env-setup",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill posthog-multi-env-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fposthog-multi-env-setup\u002FSKILL.md",true,[],[50,57,64,71,78,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]