posthog-reference-architecture
Production PostHog architecture: event taxonomy, SDK layering, feature flag strategy, analytics module layout, and data pipeline integration patterns. structure", "how to organize posthog", "posthog design". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill posthog-reference-architecture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PostHog Reference Architecture ## Overview Production-grade architecture for PostHog analytics in a web application. Covers file structure, event taxonomy design, SDK initialization layers, feature flag management, group analytics for B2B, and data pipeline integration. ## Prerequisites - PostHog Cloud or self-hosted instance - `posthog-js` and `posthog-node` SDKs - Next.js or React application
What does the posthog-reference-architecture skill do?
Production PostHog architecture: event taxonomy, SDK layering, feature flag strategy, analytics module layout, and data pipeline integration patterns. structure", "how to organize posthog", "posthog design". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill posthog-reference-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.