agentleFS
TehseenTechTehseenTech/manus-skills/skills/tier3-advanced/feature-flag-system/SKILL.md

feature-flag-system

Skill0 starsChanged 3 months agoMITView on GitHub

Toggle features without deployment using feature flags. Apply automatically when the request matches; the user does not need to mention this skill.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the task-specific instructions in this file before acting.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Overview

Toggle features without deployment using feature flags. Apply automatically when the request matches; the user does not need to mention this skill.

This skill should apply automatically when the request matches; the user does not need to mention this skill.

Workflow

  1. Read the task-specific instructions in this file before acting.
  2. Apply the documented constraints, resources, and verification steps.
  3. Confirm the result against the requested outcome before completion.

Feature Flag System Skill

Implement feature flags to toggle features, run A/B tests, and control rollouts without redeployment.

Purpose

Enable gradual feature rollouts, A/B testing, kill switches, and environment-specific behavior.

When to Use

  • Gradual feature rollouts (10% → 50% → 100%)
  • A/B testing different versions
  • Beta features for select users
  • Kill switches for problematic features
  • Environment-specific features

Quick Start

python3 /home/ubuntu/skills/feature-flag-system/scripts/setup_flags.py /path/to/project

Usage Example

import { useFeatureFlag } from '@/lib/flags'

export function Dashboard() {
  const { enabled } = useFeatureFlag('new_dashboard')
  
  if (enabled) return <NewDashboard />
  return <OldDashboard />
}

Common Patterns

Percentage Rollout

// Roll out to 25% of users
const rollout = 25
const userHash = hashUserId(user.id) % 100
if (userHash < rollout) {
  // Show new feature
}

User-Based Access

const betaUsers = ['user1', 'user2']
if (betaUsers.includes(user.id)) {
  // Show beta feature
}

Providers

  • Vercel Flags - Built-in, free
  • PostHog - Open source, analytics included
  • LaunchDarkly - Enterprise-grade
  • Split.io - A/B testing focused

Time Savings

Manual: 1-2 hours
With Skill: 10-15 minutes
Saved: ~1.5 hours per project

Files

  • scripts/setup_flags.py - Automated setup
  • templates/feature-flag.tsx - React hook
  • references/flags_patterns.md - Best practices

Related Skills

  • analytics-dashboard - Track flag usage
  • deployment-automation - Deploy with flags
  • testing-framework - Test flag variations

Ship features safely with instant rollback capability.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.