agentsclimarketplace

Feature flag system

Skill ulpi-io/plugin-marketplace/plugins/aj-geddes/skills/feature-flag-system

A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh

Install
npx -y skills add ulpi-io/plugin-marketplace --skill feature-flag-system

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.7 KB, as published. Nobody here has run it

Feature Flag System

Table of Contents

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.