feature-flags

Implement Microsoft.FeatureManagement patterns for feature toggles in ASP.NET Core.

71|10|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill feature-flags-wshaddix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flags
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/feature-flags
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill feature-flags-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of safely deploying new features, managing gradual rollouts, and enabling A/B testing within ASP.NET Core applications by leveraging feature flags.

Core Features & Use Cases

  • Configuration-Based Flags: Define feature flags directly in appsettings.json with environment-specific overrides.
  • Typed Feature Flags: Create strongly-typed constants for compile-time safety and better discoverability.
  • Razor Pages & Middleware Integration: Conditionally render UI elements and control application flow based on feature flag status.
  • Gradual Rollouts & Targeting: Implement user-based and percentage-based rollouts using targeting filters.
  • Time-Based Flags: Schedule feature availability using time window filters.
  • Use Case: You need to release a new checkout process to 10% of your users first. This Skill allows you to configure the feature flag to enable the new process for a specific percentage of users, monitor its performance, and then gradually increase the rollout or disable it if issues arise.

Quick Start

Use the feature-flags skill to enable the 'NewDashboard' feature for users in the 'BetaTesters' group.

Frequently Asked Questions about feature-flags

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement feature flags for gradual rollouts in ASP.NET Core?

You implement gradual rollouts in ASP.NET Core by configuring percentage-based filters in appsettings.json and using Microsoft.FeatureManagement.AspNetCore to control application flow based on targeted user groups.

What are feature flags and how do they work for A/B testing in ASP.NET Core?

Feature flags in ASP.NET Core are configuration toggles that enable A/B testing by conditionally rendering Razor Pages UI elements and controlling middleware flow based on targeting filters defined in appsettings.json.

Can I use Microsoft.FeatureManagement to target specific user groups for beta testing?

Yes, you can target specific user groups like BetaTesters by applying targeting filters within Microsoft.FeatureManagement, ensuring only designated audiences access new functionality during controlled release phases.

Does ASP.NET Core feature management support time-based rollouts for scheduled releases?

ASP.NET Core feature management supports scheduled releases using time window filters, allowing you to automatically activate or deactivate feature availability based on predefined date parameters without redeploying code.

How do I define strongly-typed feature flags for compile-time safety in ASP.NET Core?

Define strongly-typed feature flags by creating constants mapped to appsettings.json entries, providing compile-time safety and better discoverability when referencing feature toggles throughout your ASP.NET Core application.

Do I need the Microsoft.FeatureManagement.AspNetCore package to use feature toggles in Razor Pages?

Yes, the Microsoft.FeatureManagement.AspNetCore package is required for seamless integration, enabling feature toggles to conditionally render UI elements within Razor Pages based on current flag status.