feature-flags-are-infrastructure

SKILLWorkflowcommunauté
v0.0.0tedgoldsteinMITMis à jour il y a 3 moisSource →

Treat feature flags as first-class deployment infrastructure, not an ad-hoc `if` here and there — they decouple "what's deployed" from "what's enabled", let big features land in main as inert code, support per-user/cohort/percent rollout, and give one-config rollback. Load when a feature would other

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
1Clients
1Formats
il y a 3 moisDernière mise à jour
Skill
Auteurtedgoldstein
Version0.0.0
LicenceMIT
CatégorieWorkflow
Formatsskill.md
PromptNon publié
Compatibilité
Claude✓ Pris en charge
Cursor—
Copilot—
ChatGPT—
Gemini—
À propos

Treat feature flags as first-class deployment infrastructure, not an ad-hoc `if` here and there — they decouple "what's deployed" from "what's enabled", let big features land in main as inert code, support per-user/cohort/percent rollout, and give one-config rollback. Load when a feature would otherwise live in a long-running branch, when a risky change needs to ship 1% → 10% → 100%, when a change

Mots-clés
skillclaude

Aucune couverture des dépendances

Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.