featbit-sdks-dotnet

Included with Lifetime

$97 forever

Expert guidance for integrating FeatBit .NET Server SDK into C# and ASP.NET Core applications. Use when user asks about ".NET SDK", "C# feature flags", "ASP.NET Core FeatBit", "dotnet feature flags", or mentions .cs or .csproj files. Do not use for Node.js, Python, Java, Go, or client-side JavaScript questions.

Backend & APIs

What this skill does


# FeatBit .NET Server SDK

## When to Use This Skill

Use for server-side .NET applications — Console apps, Web API, Worker Services, and ASP.NET Core — that need real-time feature flag evaluation.

Why server-side SDK: establishes one persistent streaming connection, evaluates all flags locally, and returns results with near-zero latency on each call. Do not use for Blazor WebAssembly or MAUI — those require a client-side SDK.

## Source

https://github.com/featbit/featbit-dotnet-sdk

## Setup Workflow

Copy and track progress:
- [ ] Step 1: Install the package
- [ ] Step 2: Initialize the client
- [ ] Step 3: Evaluate the first feature flag
- [ ] Step 4: If this is ASP.NET Core, switch to dependency injection
- [ ] Step 5: If advanced behavior is needed, read the specific reference or README section

**Step 1: Install the package**

Run:

```bash
dotnet add package FeatBit.ServerSdk
```

**Step 2: Initialize the client**

Use this minimal setup:

```csharp
using FeatBit.Sdk.Server;
using FeatBit.Sdk.Server.Model;
using FeatBit.Sdk.Server.Options;

var options = new FbOptionsBuilder("<your-env-secret>")
  .Streaming(new Uri("ws://localhost:5100"))
  .Event(new Uri("http://localhost:5100"))
  .Build();

var client = new FbClient(options);
var user = FbUser.Builder("anonymous").Build();
var flagValue = client.BoolVariation("flag-key", user, defaultValue: false);
await client.CloseAsync();
```

**Step 3: Validate the integration**

If `client.Initialized` is false or the first variation returns the fallback unexpectedly, verify `EnvSecret`, `Streaming` URI, and `Event` URI, then retry.

**Step 4: If this is ASP.NET Core, use dependency injection**

Why: ensures a single `FbClient` is shared across the application lifetime and is disposed automatically when the host shuts down.

Use this pattern:

```csharp
using FeatBit.Sdk.Server.DependencyInjection;

builder.Services.AddFeatBit(options =>
{
  options.EnvSecret = "<your-env-secret>";
  options.StreamingUri = new Uri("ws://localhost:5100");
  options.EventUri = new Uri("http://localhost:5100");
});
```

Inject `IFbClient` where feature flag evaluation is needed.

## Feature Flag Evaluation

After the client is initialized, evaluate a feature flag with a user and a fallback value:

```csharp
const string flagKey = "game-runner";
var user = FbUser.Builder("anonymous").Build();

var boolVariation = client.BoolVariation(flagKey, user, defaultValue: false);
var boolVariationDetail = client.BoolVariationDetail(flagKey, user, defaultValue: false);
```

Use `BoolVariation` when only the flag value is needed. Use `BoolVariationDetail` when the user also asks why a value was returned.

## User Custom Properties

Add custom properties to `FbUser` when targeting rules depend on user attributes beyond `key` and `name`:

```csharp
var user = FbUser.Builder("a-unique-key-of-user")
  .Name("bob")
  .Custom("age", "15")
  .Custom("country", "FR")
  .Build();
```

Use built-in properties for stable identity fields. Use `Custom(key, value)` for targeting attributes that must be referenced in feature flag rules.

## Read Next Only When Needed

- Read the official README section for [evaluating flags](https://github.com/featbit/featbit-dotnet-sdk#evaluating-flags) when the user asks how to evaluate a feature flag, inspect reasons, or choose the correct variation method.
- Read the official README section for [FbUser](https://github.com/featbit/featbit-dotnet-sdk#fbuser) when the user asks about user attributes, custom properties, targeting fields, or user construction patterns.
- Read `references/openfeature-integration.md` only when the user asks about OpenFeature or the FeatBit OpenFeature provider for .NET.
- Read the official README sections for [offline mode](https://github.com/featbit/featbit-dotnet-sdk#offline-mode), [disable events collection](https://github.com/featbit/featbit-dotnet-sdk#disable-events-collection), [experiments](https://github.com/featbit/featbit-dotnet-sdk#experiments), and [dependency injection](https://github.com/featbit/featbit-dotnet-sdk#dependency-injection) only when those topics are requested.

Files: 2

Size: 7.2 KB

Complexity: 26/100

Category: Backend & APIs

Source: https://github.com/featbit/featbit-skills/tree/main/skills/featbit-sdks-dotnet

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts