feature-flag

Manage feature flags across Front, iOS, and Android codebases.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/dokdo2013/claude-code-skills --skill feature-flag-dokdo2013
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flag
Source: https://github.com/dokdo2013/claude-code-skills/tree/main/plugins/feature-flag/skills/feature-flag
Command: npx skills add https://github.com/dokdo2013/claude-code-skills --skill feature-flag-dokdo2013

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature flags let you control client functionality independently of backend changes, reducing risky deployments.

Core Features & Use Cases

  • Cross‑platform flag registry: Unified kebab‑case keys for Front, iOS, and Android.
  • Add, toggle, remove flags: Step‑by‑step guidance for safe flag lifecycle management.
  • PostHog integration: Instructions to create, test, and clean up flags in the dashboard.

Quick Start

Add a new feature flag named “my-new-feature” with default disabled using the feature‑flag skill.

Frequently Asked Questions about feature-flag

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage feature flags across frontend, iOS, and Android platforms?

To manage feature flags across frontend, iOS, and Android platforms, use a unified cross-platform flag registry that enforces consistent kebab-case keys. This ensures safe lifecycle management when adding, toggling, or deleting flags across all client codebases.

How do I add and toggle feature flags in PostHog dashboards?

You can add and toggle feature flags in PostHog dashboards by following step-by-step guidance for creating, testing, and cleaning up flags. This integrates client-side UI reactivity with backend dashboard controls for safe deployments.

Do I need kebab-case keys for feature flag management in mobile applications?

Yes, you need consistent kebab-case keys for feature flag management in mobile applications. Proper use of wrapper functions for UI reactivity is also required to ensure flags function correctly across iOS and Android codebases.

What is the best way to control client functionality independently of backend changes?

Feature flags are the best way to control client functionality independently of backend changes. They reduce risky deployments by letting you toggle specific features on or off across frontend and mobile platforms without new backend releases.

Why use wrapper functions when implementing feature flags on iOS and Android?

You use wrapper functions when implementing feature flags on iOS and Android to maintain proper UI reactivity. They ensure the application interface dynamically responds to flag state changes managed within your cross-platform flag registry.

When should I delete a feature flag from my codebase?

You should delete a feature flag from your codebase after the feature is fully stabilized and rolled out. Proper flag lifecycle management includes cleaning up the flag keys across frontend, iOS, and Android codebases, alongside PostHog dashboard removal.