[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756YMJE7485REDZD3B6AVGF":3,"skill-same:01M756YMJE7485REDZD3B6AVGF":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},"01M756YMJE7485REDZD3B6AVGF","posthog-reference-architecture",null,"Implement PostHog reference architecture with best-practice project layout.\nUse when designing new PostHog integrations, reviewing project structure,\nor establishing architecture standards for PostHog applications.\nTrigger with phrases like \"posthog architecture\", \"posthog best practices\",\n\"posthog project structure\", \"how to organize posthog\", \"posthog layout\".","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-reference-architecture\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: posthog-reference-architecture\ndescription: |\n  Implement PostHog reference architecture with best-practice project layout.\n  Use when designing new PostHog integrations, reviewing project structure,\n  or establishing architecture standards for PostHog applications.\n  Trigger with phrases like \"posthog architecture\", \"posthog best practices\",\n  \"posthog project structure\", \"how to organize posthog\", \"posthog layout\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# PostHog Reference Architecture\n\n## Overview\nProduction architecture for product analytics with PostHog. Covers event tracking design, feature flag management, experimentation framework, and integration patterns for web and backend applications.\n\n## Prerequisites\n- PostHog project (Cloud or self-hosted)\n- `posthog-js` and `posthog-node` SDKs\n- Understanding of event-driven analytics\n- Feature flag strategy planned\n\n## Architecture Diagram\n\n```\nset -euo pipefail\n┌──────────────────────────────────────────────────────┐\n│              Client Applications                      │\n│  Web (posthog-js) │ Mobile (posthog-react-native)    │\n└──────────┬────────────────────────────┬──────────────┘\n           │                            │\n           ▼                            ▼\n┌──────────────────────────────────────────────────────┐\n│              PostHog Platform                         │\n│  ┌───────────┐  ┌───────────┐  ┌─────────────────┐   │\n│  │ Events    │  │ Feature   │  │ Experiments     │   │\n│  │ & Props   │  │ Flags     │  │ (A\u002FB tests)     │   │\n│  └─────┬─────┘  └─────┬─────┘  └───────┬─────────┘   │\n│        │              │                 │             │\n│  ┌─────┴──────────────┴─────────────────┴───────┐     │\n│  │         Analytics Engine                      │     │\n│  │  Trends │ Funnels │ Retention │ Paths │ SQL  │     │\n│  └──────────────────────────────────────────────┘     │\n├──────────────────────────────────────────────────────┤\n│  Backend (posthog-node)                               │\n│  Server Events │ Flag Evaluation │ Group Analytics   │\n└──────────────────────────────────────────────────────┘\n```\n\n## Instructions\n\n### Step 1: Event Taxonomy Design\n```typescript\n\u002F\u002F events.ts - Define your event taxonomy\nexport const EVENTS = {\n  \u002F\u002F User lifecycle\n  USER_SIGNED_UP: 'user_signed_up',\n  USER_LOGGED_IN: 'user_logged_in',\n  USER_ONBOARDING_COMPLETED: 'user_onboarding_completed',\n\n  \u002F\u002F Core product actions\n  FEATURE_USED: 'feature_used',\n  ITEM_CREATED: 'item_created',\n  ITEM_SHARED: 'item_shared',\n  EXPORT_COMPLETED: 'export_completed',\n\n  \u002F\u002F Revenue\n  SUBSCRIPTION_STARTED: 'subscription_started',\n  SUBSCRIPTION_UPGRADED: 'subscription_upgraded',\n  SUBSCRIPTION_CANCELED: 'subscription_canceled',\n} as const;\n\n\u002F\u002F Standard properties for consistency\ninterface EventProperties {\n  feature_name?: string;\n  source?: 'web' | 'mobile' | 'api';\n  plan_tier?: 'free' | 'pro' | 'enterprise';\n  duration_ms?: number;\n}\n```\n\n### Step 2: Client-Side Integration\n```typescript\nimport posthog from 'posthog-js';\n\nposthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY!, {\n  api_host: 'https:\u002F\u002Fus.i.posthog.com',\n  capture_pageview: true,\n  capture_pageleave: true,\n  autocapture: true,\n  persistence: 'localStorage+cookie',\n  loaded: (ph) => {\n    if (process.env.NODE_ENV === 'development') {\n      ph.opt_out_capturing(); \u002F\u002F Disable in dev\n    }\n  },\n});\n\n\u002F\u002F Identify users\nfunction identifyUser(userId: string, traits: Record\u003Cstring, any>) {\n  posthog.identify(userId, {\n    email: traits.email,\n    plan: traits.plan,\n    company: traits.company,\n  });\n\n  \u002F\u002F Set group for company-level analytics\n  if (traits.companyId) {\n    posthog.group('company', traits.companyId, {\n      name: traits.company,\n      plan: traits.plan,\n    });\n  }\n}\n```\n\n### Step 3: Feature Flag Architecture\n```typescript\n\u002F\u002F flags.ts - Feature flag definitions\nexport const FLAGS = {\n  NEW_DASHBOARD: 'new-dashboard-v2',\n  AI_FEATURES: 'ai-features-beta',\n  PRICING_EXPERIMENT: 'pricing-page-experiment',\n} as const;\n\n\u002F\u002F React hook for feature flags\nfunction useFeatureFlag(flagKey: string) {\n  const [enabled, setEnabled] = useState(false);\n\n  useEffect(() => {\n    posthog.onFeatureFlags(() => {\n      setEnabled(posthog.isFeatureEnabled(flagKey) ?? false);\n    });\n  }, [flagKey]);\n\n  return enabled;\n}\n\n\u002F\u002F Server-side flag evaluation\nimport { PostHog } from 'posthog-node';\nconst serverPosthog = new PostHog(process.env.POSTHOG_API_KEY!);\n\nasync function getServerFlags(userId: string) {\n  return serverPosthog.getAllFlags(userId);\n}\n```\n\n### Step 4: Experiment Tracking\n```typescript\nfunction trackExperiment(experimentKey: string, userId: string) {\n  const variant = posthog.getFeatureFlag(experimentKey);\n\n  posthog.capture('$experiment_started', {\n    $experiment_name: experimentKey,\n    $experiment_variant: variant,\n  });\n\n  return variant;\n}\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Events not appearing | SDK not initialized | Check init call and API key |\n| Flag always false | Not loaded yet | Use `onFeatureFlags` callback |\n| Missing user properties | Not identified | Call `identify` before capture |\n| High event volume | Autocapture too broad | Configure autocapture selectively |\n\n## Examples\n\n### Funnel Tracking Setup\n```typescript\n\u002F\u002F Track a conversion funnel\nposthog.capture(EVENTS.ITEM_CREATED, { source: 'web' });\nposthog.capture(EVENTS.ITEM_SHARED, { share_method: 'link' });\nposthog.capture(EVENTS.EXPORT_COMPLETED, { format: 'pdf' });\n```\n\n## Resources\n- [PostHog Documentation](https:\u002F\u002Fposthog.com\u002Fdocs)\n- [PostHog Feature Flags](https:\u002F\u002Fposthog.com\u002Fdocs\u002Ffeature-flags)\n- [PostHog Experiments](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fexperiments)\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 Reference Architecture\n\n## Overview\nProduction architecture for product analytics with PostHog. Covers event tracking design, feature flag management, experimentation framework, and integration patterns for web and backend applications.\n\n## Prerequisites\n- PostHog project (Cloud or self-hosted)\n- `posthog-js` and `posthog-node` SDKs\n- Understanding of event-driven analytics\n- Feature flag strategy planned\n\n## Architecture Diagram\n\n```\nset -euo pipefail\n┌──────────────────────────────────────────────────────┐\n│              Client Applications                      │\n│  Web (posthog-js) │ Mobile (posthog-react-native)    │\n└──────────┬────────────────────────────┬──────────────┘\n           │                            │\n           ▼                            ▼\n┌──────────────────────────────────────────────────────┐\n│              PostHog Platform                         │\n│  ┌───────────┐  ┌───────────┐  ┌─────────────────┐   │\n│  │ Events    │  │ Feature   │  │ Experiments     │   │\n│  │ & Props   │  │ Flags     │  │ (A\u002FB tests)     │   │\n│  └─────┬─────┘  └─────┬─────┘  └───────┬─────────┘   │\n│        │              │                 │             │\n│  ┌─────┴──────────────┴─────────────────┴───────┐     │\n│  │         Analytics Engine                      │     │\n│  │  Trends │ Funnels │ Retention │ Paths │ SQL  │     │\n│  └──────────────────────────────────────────────┘     │\n├──────────────────────────────────────────────────────┤\n│  Backend (posthog-node)                               │\n│  Server Events │ Flag Evaluation │ Group Analytics   │\n└──────────────────────────────────────────────────────┘\n```\n\n## Instructions\n\n### Step 1: Event Taxonomy Design\n```typescript\n\u002F\u002F events.ts - Define your event taxonomy\nexport const EVENTS = {\n  \u002F\u002F User lifecycle\n  USER_SIGNED_UP: 'user_signed_up',\n  USER_LOGGED_IN: 'user_logged_in',\n  USER_ONBOARDING_COMPLETED: 'user_onboarding_completed',\n\n  \u002F\u002F Core product actions\n  FEATURE_USED: 'feature_used',\n  ITEM_CREATED: 'item_created',\n  ITEM_SHARED: 'item_shared',\n  EXPORT_COMPLETED: 'export_completed',\n\n  \u002F\u002F Revenue\n  SUBSCRIPTION_STARTED: 'subscription_started',\n  SUBSCRIPTION_UPGRADED: 'subscription_upgraded',\n  SUBSCRIPTION_CANCELED: 'subscription_canceled',\n} as const;\n\n\u002F\u002F Standard properties for consistency\ninterface EventProperties {\n  feature_name?: string;\n  source?: 'web' | 'mobile' | 'api';\n  plan_tier?: 'free' | 'pro' | 'enterprise';\n  duration_ms?: number;\n}\n```\n\n### Step 2: Client-Side Integration\n```typescript\nimport posthog from 'posthog-js';\n\nposthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY!, {\n  api_host: 'https:\u002F\u002Fus.i.posthog.com',\n  capture_pageview: true,\n  capture_pageleave: true,\n  autocapture: true,\n  persistence: 'localStorage+cookie',\n  loaded: (ph) => {\n    if (process.env.NODE_ENV === 'development') {\n      ph.opt_out_capturing(); \u002F\u002F Disable in dev\n    }\n  },\n});\n\n\u002F\u002F Identify users\nfunction identifyUser(userId: string, traits: Record\u003Cstring, any>) {\n  posthog.identify(userId, {\n    email: traits.email,\n    plan: traits.plan,\n    company: traits.company,\n  });\n\n  \u002F\u002F Set group for company-level analytics\n  if (traits.companyId) {\n    posthog.group('company', traits.companyId, {\n      name: traits.company,\n      plan: traits.plan,\n    });\n  }\n}\n```\n\n### Step 3: Feature Flag Architecture\n```typescript\n\u002F\u002F flags.ts - Feature flag definitions\nexport const FLAGS = {\n  NEW_DASHBOARD: 'new-dashboard-v2',\n  AI_FEATURES: 'ai-features-beta',\n  PRICING_EXPERIMENT: 'pricing-page-experiment',\n} as const;\n\n\u002F\u002F React hook for feature flags\nfunction useFeatureFlag(flagKey: string) {\n  const [enabled, setEnabled] = useState(false);\n\n  useEffect(() => {\n    posthog.onFeatureFlags(() => {\n      setEnabled(posthog.isFeatureEnabled(flagKey) ?? false);\n    });\n  }, [flagKey]);\n\n  return enabled;\n}\n\n\u002F\u002F Server-side flag evaluation\nimport { PostHog } from 'posthog-node';\nconst serverPosthog = new PostHog(process.env.POSTHOG_API_KEY!);\n\nasync function getServerFlags(userId: string) {\n  return serverPosthog.getAllFlags(userId);\n}\n```\n\n### Step 4: Experiment Tracking\n```typescript\nfunction trackExperiment(experimentKey: string, userId: string) {\n  const variant = posthog.getFeatureFlag(experimentKey);\n\n  posthog.capture('$experiment_started', {\n    $experiment_name: experimentKey,\n    $experiment_variant: variant,\n  });\n\n  return variant;\n}\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Events not appearing | SDK not initialized | Check init call and API key |\n| Flag always false | Not loaded yet | Use `onFeatureFlags` callback |\n| Missing user properties | Not identified | Call `identify` before capture |\n| High event volume | Autocapture too broad | Configure autocapture selectively |\n\n## Examples\n\n### Funnel Tracking Setup\n```typescript\n\u002F\u002F Track a conversion funnel\nposthog.capture(EVENTS.ITEM_CREATED, { source: 'web' });\nposthog.capture(EVENTS.ITEM_SHARED, { share_method: 'link' });\nposthog.capture(EVENTS.EXPORT_COMPLETED, { format: 'pdf' });\n```\n\n## Resources\n- [PostHog Documentation](https:\u002F\u002Fposthog.com\u002Fdocs)\n- [PostHog Feature Flags](https:\u002F\u002Fposthog.com\u002Fdocs\u002Ffeature-flags)\n- [PostHog Experiments](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fexperiments)\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","Implement PostHog reference architecture with best-practice project layout.\nUse when designing new PostHog integrations, reviewing project structure,\nor establishing architecture standards for PostHog applications.\nTrigger with phrases like \"posthog architecture\", \"posthog best practices\",\n\"posthog project structure\", \"how to organize posthog\", \"posthog layout\".\n","Read, Grep","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-reference-architecture",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill posthog-reference-architecture",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill posthog-reference-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fposthog-reference-architecture\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",[],[]]