Backend Feature Flags
Use when the user asks about server-side feature flags, kill switches, percentage rollouts, OpenFeature, LaunchDarkly, Unleash, Flagsmith or flag cleanup. Produces a flag design with ownership, defaults and evaluation code. Not for client UI flags (use frontend-feature-flags) or deploy strategies (use progressive-delivery).
Install
npx skills add j4flmao/agent-skills --skill backend-feature-flagsgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/backend/universal/feature-flags ~/.claude/skills/backend-feature-flagsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Backend Feature Flags ## Purpose Design feature flag systems with lifecycle management, targeting, and risk controls. ## Agent Protocol ### Trigger Exact user phrases: "feature flag", "feature toggle", "canary release", "gradual rollout", "A/B test", "kill switch", "flag management", "LaunchDarkly", "Unleash", "flag evaluation", "targeting rule", "percentage rollout", "feature gate". ### Input Context Before activating, verify: - Number of flags expected (10s, 100s, 1000s) - Targeting requirements (user ID, group, percentage, custom attributes) - Flag lifespan (short-lived release toggles vs long-lived ops toggles) - Evaluation performance needs (latency budget, cache TTL tolerance) - Flag management platform (LaunchDarkly, Unleash, Flagsmith, custom) ### Output Artifact Feature flag strategy as formatted text. ### Response Format ```yaml # Flag definitions with targeting rules # Evaluation configuration ``` ```typescript // Flag evaluation code // SDK setup ``` No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick. ### Completion Criteria - [ ] Flag types classified (release/experiment/ops/permission) - [ ] Evaluation strategy with caching and bulk evaluation - [ ] Targeting rules defined (user, group, percentage, prerequisites) - [ ] Flag lifecycle with creation, evaluation, stabilization, cleanup - [ ] Risk controls (kill switch, auto-rollback, audit log)
Details
- Skill name
backend-feature-flags- Repository
- j4flmao/agent-skills
- Path
skills/backend/universal/feature-flags/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Backend Feature Flags skill do?
Use when the user asks about server-side feature flags, kill switches, percentage rollouts, OpenFeature, LaunchDarkly, Unleash, Flagsmith or flag cleanup. Produces a flag design with ownership, defaults and evaluation code. Not for client UI flags (use frontend-feature-flags) or deploy strategies (use progressive-delivery).
How do I install the Backend Feature Flags skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill backend-feature-flags. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Backend Feature Flags popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Backend File Storage
45j4flmao/agent-skills
Use when the user asks about file uploads, S3 presigned URLs, direct-to-storage uploads, object keys, Azure Blob or GCS, CDN delivery of files, virus scanning or lifecycle policies. Produces an upload and storage design with validation. Not for CSV data imports (use backend-bulk-import).
Backend Event Sourcing
45j4flmao/agent-skills
Use when the user asks about event sourcing, storing every change as an append-only event log, event store, rehydrating aggregates, snapshots, upcasting or projection rebuilds. Produces an event-sourced aggregate and store design. Not for CQRS without event sourcing (use backend-cqrs-patterns).
Backend Graphql Patterns
45j4flmao/agent-skills
Use when the user asks about GraphQL schema design, resolvers, fixing N+1 queries in GraphQL resolvers, DataLoader, cursor pagination, query depth/complexity limits or persisted queries. Produces schema and resolver code. Not for subgraph composition (use api-graphql-federation).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.