setup-feature-flags

Feature flags decouple deployment from release by gating code paths behind typed flag keys evaluated at runtime, enabling controlled rollouts and immediate kill switches without redeploying. This skill provides registry and in-memory client implementations to manage this process.

A kill switch disables a feature instantly by toggling its flag state. This skill enables kill switches via a centralized flag registry and middleware integration, allowing you to quickly turn off problematic releases like a new billing engine without code changes.

Deterministic rollout ensures consistent evaluation by using per-user context and typed flag keys. This skill implements an in-memory client that evaluates flags deterministically, supporting overrides and context propagation for precise rollout strategies.

Feature flags integrate into service middleware via a flag-aware layer that propagates evaluation context across services. This skill covers middleware integration patterns, ensuring flags are consistently evaluated within cloud-agnostic service pipelines.

Yes, a flag registry centralizes feature flag definitions with ownership, rollout, and expiration metadata. This skill implements a registry pattern to maintain lifecycle control and prevent stale flags from accumulating in your codebase.

No, this skill relies on an in-memory client implementation with no external dependencies. It provides deterministic evaluation, overrides, and testing capabilities directly within your application runtime.