Feature Flags Dotnet — Agent Skill by PostHog

From the author

PostHog feature flags for .NET applications

— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides guidance and best practices for implementing PostHog feature flags within .NET applications. It covers the integration process, architectural considerations for flag management, and strategies for maintaining clean code while using feature toggles. The skill emphasizes server-side evaluation, secure configuration via environment variables, and operational best practices to ensure consistent user experiences and reliable feature deployments.

What it does

Provides instructions for integrating PostHog feature flags into .NET projects.
Outlines best practices for flag naming, targeting, and lifecycle management.
Recommends architectural patterns to minimize code complexity when using flags.
Supports management of flags directly via PostHog MCP tools if available.
Advises on performance optimization through local evaluation and bootstrapping.

When to use it

When you need to perform controlled feature rollouts or A/B testing in a .NET application.
When you want to decouple feature deployment from code releases.
When you need to manage feature availability based on user properties or groups.
When you are looking for standardized patterns to maintain feature flag code in a .NET codebase.

Advantages

Enables safer, incremental feature releases.
Reduces the risk of deploying broken features to all users simultaneously.
Promotes clean code by encouraging centralized flag handling.
Improves performance by supporting server-side and local flag evaluation.

Usage examples

“How do I check a boolean feature flag in my .NET application?”: The agent will provide the standard pattern for calling the PostHog SDK to evaluate a boolean flag, ensuring the logic is wrapped appropriately to maintain code readability.
“What are the best practices for naming feature flags?”: The agent will suggest using descriptive, positive-language names that reflect the flag's purpose and return type, such as 'is_premium_user' for booleans.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/posthog/feature-flags-dotnet/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip feature-flags-dotnet.zip -d .agents/skills

Documentation by PostHog

PostHog feature flags for .NET

This skill helps you add PostHog feature flags to .NET applications.

Reference files

references/dotnet.md - .net 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

No specific framework guidelines.

Files

ATTRIBUTION.mdAdded by AutoGineer960 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md1.3 KiB
references/adding-feature-flag-code.md108.7 KiB
references/best-practices.md7.9 KiB
references/dotnet.md6.8 KiB

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an MCP server

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Claude API
AnthropicOfficial
Comprehensive reference for integrating Anthropic's Claude API, SDKs, and Managed Agents into your applications.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0Medium riskHas scriptsGitHub stars of the source repository188.6k
Transformers
K-Dense· Community
Integrate Hugging Face Transformers for model loading, inference, and fine-tuning across NLP, vision, and audio tasks.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository56.4k
Open Notebook
K-Dense· Community
Integrate with the self-hosted Open Notebook platform to automate research ingestion, context-aware chat, and AI-driven analysis.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository56.4k
Vision Sft
Seth Hobson· Community
A structured workflow for supervised fine-tuning of vision-language models, focusing on adapter configuration and silent failure prevention.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
LLM Evaluation
Seth Hobson· Community
A comprehensive framework for evaluating LLM application performance using automated metrics, human feedback, and LLM-as-a-judge techniques.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Lora Qlora Recipes
Seth Hobson· Community
Provides configuration recipes and best-practice hyperparameters for LoRA and QLoRA supervised fine-tuning.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k