PostHog feature flags for Node.js
SkillDev toolsThis skill helps you add PostHog feature flags to Node.js applications.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the PostHog feature flags for Node.js skill
About this skill
PostHog feature flags for Node.js applications
What this skill tells your AI
The instructions your AI receives, as published by posthog/skills in skills/posthog/all/skills/feature-flags-nodejs/SKILL.md and read by ahel’s review.
This skill helps you add PostHog feature flags to Node.js applications.
Reference files
references/nodejs.md- Node.js feature flags installation - docsreferences/adding-feature-flag-code.md- Adding feature flag code - docsreferences/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
No specific framework guidelines.
Signals
- GitHub stars
- 71
- Forks
- 7
- Last commit
- Sep 2026
ahel review
K1binfo
installs-packages (in references/nodejs.md)
Automated review, not a security audit. Ruleset v1+k2.
Others that do the same job
Advanced
- Item type
- skill
- Key
feature-flags-nodejs- Source
- github.com/posthog/skills