Feature Flag System

SkillCloud & infra

Implement feature flags (toggles) for controlled feature rollouts, A/B testing, canary deployments, and kill switches. Use when deploying new features gradually, testing in production, or managing feature lifecycles.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Feature Flag System skill

What this skill tells your AI

The instructions your AI receives, as published by aj-geddes/useful-ai-prompts in skills/feature-flag-system/SKILL.md and read by ahel’s review.

Table of Contents

  • Overview
  • When to Use
  • Quick Start
  • Reference Guides
  • Best Practices

Overview

Implement feature flags to decouple deployment from release, enable gradual rollouts, A/B testing, and provide emergency kill switches.

When to Use

  • Gradual feature rollouts
  • A/B testing and experiments
  • Canary deployments
  • Beta features for specific users
  • Emergency kill switches
  • Trunk-based development
  • Dark launching
  • Operational flags (maintenance mode)
  • User-specific features

Quick Start

Minimal working example:

interface FlagConfig {
  key: string;
  enabled: boolean;
  description: string;
  rules?: FlagRule[];
  variants?: FlagVariant[];
  createdAt: Date;
  updatedAt: Date;
}

interface FlagRule {
  type: "user" | "percentage" | "attribute" | "datetime";
  operator: "in" | "equals" | "contains" | "gt" | "lt" | "between";
  attribute?: string;
  values: any[];
}

interface FlagVariant {
  key: string;
  weight: number;
  value: any;
}

interface EvaluationContext {
  userId?: string;
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Feature Flag Service (TypeScript)Feature Flag Service (TypeScript)
React Hook for Feature FlagsReact Hook for Feature Flags
Feature Flag with AnalyticsFeature Flag with Analytics
LaunchDarkly-Style SDKLaunchDarkly-Style SDK
Admin UI for Feature FlagsAdmin UI for Feature Flags

Best Practices

✅ DO

  • Use descriptive flag names
  • Document flag purpose and lifecycle
  • Implement gradual rollouts
  • Track flag evaluations
  • Clean up old flags regularly
  • Use feature flags for experiments
  • Implement kill switches for critical features
  • Test both enabled and disabled states
  • Use consistent hashing for stable rollouts
  • Provide admin UI for non-technical users

❌ DON'T

  • Use flags for permanent configuration
  • Accumulate technical debt with old flags
  • Skip flag cleanup
  • Make flags too granular
  • Hard-code flag checks everywhere
  • Skip analytics and monitoring

Signals

GitHub stars
336
Forks
55
Last commit
Mar 2026
Advanced
Catalog kind
skill
Gateway key
feature-flag-system
Source
github.com/aj-geddes/useful-ai-prompts