skills/tier3-advanced/feature-flag-system/SKILL.md
Toggle features without deployment using feature flags
npx skillsauth add abcnuts/manus-skills feature-flag-systemInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Implement feature flags to toggle features, run A/B tests, and control rollouts without redeployment.
Enable gradual feature rollouts, A/B testing, kill switches, and environment-specific behavior.
python3 /home/ubuntu/skills/feature-flag-system/scripts/setup_flags.py /path/to/project
import { useFeatureFlag } from '@/lib/flags'
export function Dashboard() {
const { enabled } = useFeatureFlag('new_dashboard')
if (enabled) return <NewDashboard />
return <OldDashboard />
}
// Roll out to 25% of users
const rollout = 25
const userHash = hashUserId(user.id) % 100
if (userHash < rollout) {
// Show new feature
}
const betaUsers = ['user1', 'user2']
if (betaUsers.includes(user.id)) {
// Show beta feature
}
Manual: 1-2 hours
With Skill: 10-15 minutes
Saved: ~1.5 hours per project
scripts/setup_flags.py - Automated setuptemplates/feature-flag.tsx - React hookreferences/flags_patterns.md - Best practicesanalytics-dashboard - Track flag usagedeployment-automation - Deploy with flagstesting-framework - Test flag variationsShip features safely with instant rollback capability.
tools
Generate comprehensive demonstrations showing how to access projects and work across different environments (Manus terminals, personal computers, team collaboration). Use when users ask "how do I access this from another terminal/computer", "how do I share this with my team", "how do I get this on my Mac", or need clarification on Manus persistence vs GitHub usage.
development
Use when you have a spec or requirements for a multi-step task, before touching code
data-ai
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
development
Use when implementing any feature or bugfix, before writing implementation code