feature-toggle

Add per-customer feature flags to show or hide UI features.

9|Updated Dec 21, 2025

Search Tags:#frontend #backend #subscription #feature-flag #toggle #per-customer #admin-override

Ready to run

npx skills add https://github.com/gewoonseba/dotfiles --skill feature-toggle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-toggle
Source: https://github.com/gewoonseba/dotfiles/tree/main/claude/.claude/skills/feature-toggle
Command: npx skills add https://github.com/gewoonseba/dotfiles --skill feature-toggle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a per-customer feature toggle to show/hide a UI feature.

Core Features & Use Cases

Store feature flags on the Organization model and expose through the subscription service as SubscriptionFeature objects.
Enable/disable features per customer, including admin override support for global admins with a subscription debugger.
Wire up backend enum, subscription data, service logic, and frontend usage to gate UI behavior.

Quick Start

Create a new feature flag end-to-end and verify the per-customer gating in both backend and frontend, including the admin override path.

Frequently Asked Questions about feature-toggle

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

FAQPage Schema

How do I implement per-customer feature flags to gate UI behavior?▼

Feature flags enable per-customer toggling by storing flags on the Organization model and exposing them through the subscription service as SubscriptionFeature objects. This allows you to gate UI behavior by checking the active status of specific features for individual customers.

What is an admin override pathway for feature toggles?▼

An admin override pathway for feature toggles allows global admins to bypass per-customer gating using a subscription debugger. This enables administrators to manually enable or disable features for specific customers regardless of their standard subscription configuration.

How do I wire up backend enums and subscription data for feature gating?▼

To wire backend enums and subscription data for feature gating, create a FeatureFlags entry, add a has_my_feature field, and connect the subscription service logic. This ensures the backend properly evaluates active and inactive feature states per customer.

How does the frontend access per-customer feature flag states?▼

The frontend accesses per-customer feature flag states via the customer.subscription.has_my_feature.active path. This exposes the toggle status directly to UI components, allowing them to conditionally render features based on the customer's subscription data.

Do I need tests for both active and inactive feature flag states?▼

Tests covering both active and inactive feature flag states are required. Verifying both states ensures the per-customer gating logic functions correctly across backend service wiring and frontend consumption, preventing unintended feature access.