feature-flag-patterns
Gradual rollout strategies, kill switches, A/B testing integration, flag lifecycle management, and technical debt prevention.
Profile →npx skills add vibeeval/vibecosystem --skill feature-flag-patterns --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Feature Flag Patterns Feature flag strategies for safe deployments, experimentation, and operational control. ## Flag Types and Structure ```typescript interface FeatureFlag { key: string type: 'boolean' | 'percentage' | 'variant' | 'segment' enabled: boolean description: string owner: string // Team/person responsible createdAt: Date expiresAt?: Date // Auto-cleanup reminder tags: string[] // 'release', 'experiment', 'ops', 'permission' } // Flag categories by lifecycle enum FlagCategory { RELEASE = 'release', // Temporary: ship behind flag, remove after rollout EXPERIMENT = 'experiment', // Temporary: A/B test, remove after analysis OPS = 'ops', // Long-lived: kill switches, circuit breakers PERMISSION = 'permission', // Long-lived: premium features, entitlements } // Flag configuration const FLAGS: Record<string, FeatureFlag> = { 'new-checkout-flow': { key: 'new-checkout-flow', type: 'percentage', enabled: true, description: 'Redesigned checkout with fewer steps', owner: 'checkout-team', createdAt: new Date('2025-01-15'), expiresAt: new Date('2025-04-15'), // 3 month max tags: ['release'], }, 'emergency-read-only': { key: 'emergency-read-only', type: 'boolean', enabled: false,
- Flag Types and Structure
- Gradual Rollout
- Kill Switch Pattern
- A/B Testing Integration
- Flag Lifecycle and Cleanup
- Checklist
- Anti-Patterns
What does the feature-flag-patterns skill do?
Gradual rollout strategies, kill switches, A/B testing integration, flag lifecycle management, and technical debt prevention.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill feature-flag-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.