[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ADM239JX8N1MPC36NBAZJF":3,"skill-same:01M7ADM239JX8N1MPC36NBAZJF":106},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M7ADM239JX8N1MPC36NBAZJF","feature-flags-architect",null,"Use when adding, retiring, or auditing feature flags. Triggers on \"add a flag\", \"ship behind a flag\", \"rollout plan\", \"kill switch\", \"stale flags\", \"flag debt\", \"LaunchDarkly\", \"GrowthBook\", \"Statsig\", \"Unleash\", \"Flipt\", or any progressive-delivery question. Ships flag debt scanner, rollout planner, and kill-switch auditor (all stdlib Python), 4 references on flag taxonomy + provider trade-offs + rollout strategies + lifecycle, plus a \u002Fflag-cleanup slash command.","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: feature-flags-architect\ndescription: Use when adding, retiring, or auditing feature flags. Triggers on \"add a flag\", \"ship behind a flag\", \"rollout plan\", \"kill switch\", \"stale flags\", \"flag debt\", \"LaunchDarkly\", \"GrowthBook\", \"Statsig\", \"Unleash\", \"Flipt\", or any progressive-delivery question. Ships flag debt scanner, rollout planner, and kill-switch auditor (all stdlib Python), 4 references on flag taxonomy + provider trade-offs + rollout strategies + lifecycle, plus a \u002Fflag-cleanup slash command.\ncontext: fork\nversion: 2.9.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [feature-flags, progressive-delivery, rollout, kill-switch, launchdarkly, growthbook, statsig, unleash, flipt, release-engineering]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# Feature Flags Architect\n\nEnd-to-end discipline for feature flags: classify them, ship them, ramp them, and retire them. Most teams treat flags as throwaway `if`-statements; this skill treats them as a controlled lifecycle with measurable debt.\n\n## When to use\n\n- Adding a new flag and need a rollout plan\n- Auditing a codebase for stale or orphaned flags\n- Choosing a flag provider (LaunchDarkly vs GrowthBook vs Statsig vs Unleash vs Flipt vs build-your-own)\n- Designing a kill-switch path for a risky launch\n- Cleaning up flag debt before a release freeze\n- Reviewing whether a feature should ship behind a flag at all\n\n## Core principle: flags are a lifecycle, not an `if`\n\n```\nrequest → design → ship → ramp → cleanup → archive\n```\n\nFlags that skip cleanup become debt: dead branches, stale defaults, untested code paths, unbounded blast radius. The three scripts in this skill enforce the lifecycle.\n\n## Quick start\n\n```bash\n# 1. Audit the repo for flag debt\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 90\n\n# 2. Plan a progressive rollout for a new flag\npython scripts\u002Frollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring\n\n# 3. Verify every flag has a documented kill switch\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc docs\u002Ffeature-flags.md\n```\n\n## The 4 flag types (taxonomy)\n\nDifferent flag types have different lifespans and ownership. Misclassifying creates debt.\n\n| Type | Purpose | Typical lifespan | Owner | Cleanup trigger |\n|---|---|---|---|---|\n| **Release** | Hide unfinished features in production | days–weeks | Eng | 100% rollout reached |\n| **Experiment** | A\u002FB test variants | weeks | Product\u002FMarketing | Test concluded; winner picked |\n| **Operational** | Circuit breakers, perf toggles, kill switches | months–years | Eng\u002FSRE | Replaced by autoscaling\u002Ffeature retirement |\n| **Permission** | Entitlements per user\u002Faccount\u002Fplan | years (permanent) | Product | Plan\u002Frole removed |\n\nOnly Release and Experiment flags should be on a debt-scanner watchlist. Operational and Permission flags are by design long-lived. See `references\u002Fflag_taxonomy.md` for decision tree.\n\n## The 3 Python tools\n\nAll three are stdlib-only. Run with `--help`.\n\n### `flag_debt_scanner.py`\n\nFinds flags older than `--max-age-days` with low usage, suggesting candidates for cleanup.\n\n```bash\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 90 --format text\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 60 --format json > debt.json\n```\n\n**Detection heuristic:**\n1. Walk `--repo` for code references matching common flag-call patterns:\n   - `flag(\"...\")`, `isFlagEnabled(\"...\")`, `featureFlag(\"...\")`, `getFlag(\"...\")`\n   - `client.variation(\"...\", ...)`, `unleash.isEnabled(\"...\")`, `growthbook.feature(\"...\")`\n2. For each unique flag identifier, find the oldest commit that introduced it (`git log --diff-filter=A -S \u003Cname>`).\n3. Flag as DEBT if introduced > `--max-age-days` ago AND used in ≤`--min-uses` places.\n\nOutputs flag name, age in days, file references, suggested action. JSON mode is CI-friendly.\n\n### `rollout_planner.py`\n\nGenerates a phased rollout schedule from population size, target percent, duration, and strategy.\n\n```bash\npython scripts\u002Frollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring\npython scripts\u002Frollout_planner.py --population 50000 --target-percent 25 --duration-days 7 --strategy linear\npython scripts\u002Frollout_planner.py --population 1000000 --target-percent 100 --duration-days 30 --strategy log\n```\n\n**Strategies:**\n- `ring`: 1% → 5% → 25% → 50% → 100%, evenly spaced. Default for risky launches.\n- `linear`: constant rate per day. Default for medium-risk.\n- `log`: rapid early, slow tail. Default for low-risk launches with confidence.\n- `cohort`: by named cohort (internal → beta → free → paid → all).\n\nOutputs a markdown table with date, percent, expected user count, abort criteria, and verification step per phase.\n\n### `kill_switch_audit.py`\n\nCross-references code-discovered flags against documentation to verify each has a kill switch path written down.\n\n```bash\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc docs\u002Ffeature-flags.md\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc runbooks\u002Fflags.md --format json\n```\n\n**What it checks:**\n1. Every code-discovered flag has an entry in `--flag-doc`\n2. Each entry declares: owner, type, kill-switch trigger, monitoring dashboard\n3. Reports flags missing documentation (FAIL) or missing fields (WARN)\n\nUse as a pre-merge gate before any new flag ships.\n\n## Provider chooser (5 + DIY)\n\n| Provider | Best for | Pricing model | Lock-in risk | OSS option |\n|---|---|---|---|---|\n| **LaunchDarkly** | Enterprise, complex targeting, audit\u002Fcompliance | Per-MAU, expensive | High | No |\n| **GrowthBook** | Mid-market, A\u002FB testing focused, OSS-friendly | Per-MAU + OSS | Low | Yes (self-host) |\n| **Statsig** | Growth\u002Fproduct teams, advanced experimentation | Free tier + per-MAU | Medium | No |\n| **Unleash** | OSS-first, self-hosted, dev-friendly | OSS + Enterprise | Low | Yes |\n| **Flipt** | Lightweight, k8s-native, simple needs | OSS-only | None | Yes |\n| **DIY** | \u003C100 flags, no targeting, full control | None | None | N\u002FA |\n\nDecision rules:\n- \u003C50 flags + no targeting → DIY with config file or env vars\n- Need analytics + experimentation → Statsig or GrowthBook\n- Compliance\u002FSOC2 audit logs required → LaunchDarkly\n- Self-hosting required (data residency \u002F air-gapped) → Unleash or Flipt\n- See `references\u002Fprovider_comparison.md` for detail.\n\n## Workflows\n\n### Workflow 1: Ship a new feature behind a flag\n\n```\n1. Classify: which of the 4 flag types?\n   → Release (most common for engineering work)\n2. Run rollout_planner.py to design the ramp\n3. Add flag entry to docs\u002Ffeature-flags.md BEFORE writing code:\n   - name, owner, type, kill-switch trigger, dashboard URL\n4. Write the code with the flag\n5. Run kill_switch_audit.py — must pass before merge\n6. Deploy at 0%; verify kill switch works\n7. Execute rollout schedule; abort if abort criteria met\n8. At 100% for 7+ days: remove flag, delete dead branch, archive doc entry\n```\n\n### Workflow 2: Quarterly flag cleanup\n\n```\n1. Run flag_debt_scanner.py --repo . --max-age-days 90 > debt.md\n2. For each flagged item:\n   a. Confirm it reached 100% (or was killed)\n   b. Find the issue\u002FPR that introduced it; verify owner agrees to remove\n   c. Delete dead branches; remove flag config\n   d. Run kill_switch_audit.py — should now show one fewer flag\n3. Update CHANGELOG: \"Removed N stale flags\"\n```\n\n### Workflow 3: Choose a provider\n\n```\n1. Estimate flag count (current + 12-month projection)\n2. Required features:\n   - Targeting rules (user, account, geo, %)?\n   - A\u002FB testing + stats?\n   - Audit log \u002F SOC2?\n   - Self-hosting \u002F data residency?\n3. Pricing budget (MAU * cost-per-MAU)\n4. See provider_comparison.md decision tree\n5. Build a 30-day proof-of-concept before signing\n```\n\n### Workflow 4: Design a kill switch\n\n```\n1. Identify the failure modes:\n   - Latency spike (which threshold?)\n   - Error rate spike (which threshold?)\n   - Business metric regression (which threshold?)\n2. Wire each to an abort:\n   - Manual: dashboard link + on-call playbook\n   - Automated: alert threshold flips flag back to 0%\n3. Test the kill switch in staging BEFORE production rollout\n4. Document in flag-doc; pass kill_switch_audit.py\n```\n\n## References\n\n- `references\u002Fflag_taxonomy.md` — 4 types, decision tree, ownership, lifespan\n- `references\u002Fprovider_comparison.md` — LaunchDarkly \u002F GrowthBook \u002F Statsig \u002F Unleash \u002F Flipt \u002F DIY trade-offs\n- `references\u002Frollout_strategies.md` — ring \u002F linear \u002F log \u002F cohort \u002F geo, abort criteria, monitoring\n- `references\u002Fflag_lifecycle.md` — request → design → ship → ramp → cleanup → archive\n\n## Slash command\n\n`\u002Fflag-cleanup` — Run the full cleanup workflow on the current repo: scan for debt, generate a removal plan, audit kill switches.\n\n## Asset templates\n\n- `assets\u002Fflag_request_template.md` — fill-in form for new flag requests (name, owner, type, kill switch, rollout plan)\n\n## Anti-patterns\n\n- **Permanent flag with `if (FLAG_FOO)` 50 places** — should be a Permission flag with a runtime config, not a Release flag\n- **Flag with no owner** — when the original engineer leaves, no one cleans it up\n- **No kill switch documented** — when the feature breaks, no one knows how to disable it\n- **A\u002FB test that ran 6 months** — pick a winner; running indefinitely is debt\n- **Flags as feature toggles for cosmetic changes** — ship via deploy, not flag\n\n## Verifiable success\n\nA team using this skill should achieve:\n- 100% of new flags pass `kill_switch_audit.py` at merge time\n- `flag_debt_scanner.py --max-age-days 90` returns ≤5 stale flags repo-wide\n- Every flag has a documented owner, type, and kill switch\n- Mean time to retire a Release flag: \u003C60 days from 100% rollout\n","# Feature Flags Architect\n\nEnd-to-end discipline for feature flags: classify them, ship them, ramp them, and retire them. Most teams treat flags as throwaway `if`-statements; this skill treats them as a controlled lifecycle with measurable debt.\n\n## When to use\n\n- Adding a new flag and need a rollout plan\n- Auditing a codebase for stale or orphaned flags\n- Choosing a flag provider (LaunchDarkly vs GrowthBook vs Statsig vs Unleash vs Flipt vs build-your-own)\n- Designing a kill-switch path for a risky launch\n- Cleaning up flag debt before a release freeze\n- Reviewing whether a feature should ship behind a flag at all\n\n## Core principle: flags are a lifecycle, not an `if`\n\n```\nrequest → design → ship → ramp → cleanup → archive\n```\n\nFlags that skip cleanup become debt: dead branches, stale defaults, untested code paths, unbounded blast radius. The three scripts in this skill enforce the lifecycle.\n\n## Quick start\n\n```bash\n# 1. Audit the repo for flag debt\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 90\n\n# 2. Plan a progressive rollout for a new flag\npython scripts\u002Frollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring\n\n# 3. Verify every flag has a documented kill switch\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc docs\u002Ffeature-flags.md\n```\n\n## The 4 flag types (taxonomy)\n\nDifferent flag types have different lifespans and ownership. Misclassifying creates debt.\n\n| Type | Purpose | Typical lifespan | Owner | Cleanup trigger |\n|---|---|---|---|---|\n| **Release** | Hide unfinished features in production | days–weeks | Eng | 100% rollout reached |\n| **Experiment** | A\u002FB test variants | weeks | Product\u002FMarketing | Test concluded; winner picked |\n| **Operational** | Circuit breakers, perf toggles, kill switches | months–years | Eng\u002FSRE | Replaced by autoscaling\u002Ffeature retirement |\n| **Permission** | Entitlements per user\u002Faccount\u002Fplan | years (permanent) | Product | Plan\u002Frole removed |\n\nOnly Release and Experiment flags should be on a debt-scanner watchlist. Operational and Permission flags are by design long-lived. See `references\u002Fflag_taxonomy.md` for decision tree.\n\n## The 3 Python tools\n\nAll three are stdlib-only. Run with `--help`.\n\n### `flag_debt_scanner.py`\n\nFinds flags older than `--max-age-days` with low usage, suggesting candidates for cleanup.\n\n```bash\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 90 --format text\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 60 --format json > debt.json\n```\n\n**Detection heuristic:**\n1. Walk `--repo` for code references matching common flag-call patterns:\n   - `flag(\"...\")`, `isFlagEnabled(\"...\")`, `featureFlag(\"...\")`, `getFlag(\"...\")`\n   - `client.variation(\"...\", ...)`, `unleash.isEnabled(\"...\")`, `growthbook.feature(\"...\")`\n2. For each unique flag identifier, find the oldest commit that introduced it (`git log --diff-filter=A -S \u003Cname>`).\n3. Flag as DEBT if introduced > `--max-age-days` ago AND used in ≤`--min-uses` places.\n\nOutputs flag name, age in days, file references, suggested action. JSON mode is CI-friendly.\n\n### `rollout_planner.py`\n\nGenerates a phased rollout schedule from population size, target percent, duration, and strategy.\n\n```bash\npython scripts\u002Frollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring\npython scripts\u002Frollout_planner.py --population 50000 --target-percent 25 --duration-days 7 --strategy linear\npython scripts\u002Frollout_planner.py --population 1000000 --target-percent 100 --duration-days 30 --strategy log\n```\n\n**Strategies:**\n- `ring`: 1% → 5% → 25% → 50% → 100%, evenly spaced. Default for risky launches.\n- `linear`: constant rate per day. Default for medium-risk.\n- `log`: rapid early, slow tail. Default for low-risk launches with confidence.\n- `cohort`: by named cohort (internal → beta → free → paid → all).\n\nOutputs a markdown table with date, percent, expected user count, abort criteria, and verification step per phase.\n\n### `kill_switch_audit.py`\n\nCross-references code-discovered flags against documentation to verify each has a kill switch path written down.\n\n```bash\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc docs\u002Ffeature-flags.md\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc runbooks\u002Fflags.md --format json\n```\n\n**What it checks:**\n1. Every code-discovered flag has an entry in `--flag-doc`\n2. Each entry declares: owner, type, kill-switch trigger, monitoring dashboard\n3. Reports flags missing documentation (FAIL) or missing fields (WARN)\n\nUse as a pre-merge gate before any new flag ships.\n\n## Provider chooser (5 + DIY)\n\n| Provider | Best for | Pricing model | Lock-in risk | OSS option |\n|---|---|---|---|---|\n| **LaunchDarkly** | Enterprise, complex targeting, audit\u002Fcompliance | Per-MAU, expensive | High | No |\n| **GrowthBook** | Mid-market, A\u002FB testing focused, OSS-friendly | Per-MAU + OSS | Low | Yes (self-host) |\n| **Statsig** | Growth\u002Fproduct teams, advanced experimentation | Free tier + per-MAU | Medium | No |\n| **Unleash** | OSS-first, self-hosted, dev-friendly | OSS + Enterprise | Low | Yes |\n| **Flipt** | Lightweight, k8s-native, simple needs | OSS-only | None | Yes |\n| **DIY** | \u003C100 flags, no targeting, full control | None | None | N\u002FA |\n\nDecision rules:\n- \u003C50 flags + no targeting → DIY with config file or env vars\n- Need analytics + experimentation → Statsig or GrowthBook\n- Compliance\u002FSOC2 audit logs required → LaunchDarkly\n- Self-hosting required (data residency \u002F air-gapped) → Unleash or Flipt\n- See `references\u002Fprovider_comparison.md` for detail.\n\n## Workflows\n\n### Workflow 1: Ship a new feature behind a flag\n\n```\n1. Classify: which of the 4 flag types?\n   → Release (most common for engineering work)\n2. Run rollout_planner.py to design the ramp\n3. Add flag entry to docs\u002Ffeature-flags.md BEFORE writing code:\n   - name, owner, type, kill-switch trigger, dashboard URL\n4. Write the code with the flag\n5. Run kill_switch_audit.py — must pass before merge\n6. Deploy at 0%; verify kill switch works\n7. Execute rollout schedule; abort if abort criteria met\n8. At 100% for 7+ days: remove flag, delete dead branch, archive doc entry\n```\n\n### Workflow 2: Quarterly flag cleanup\n\n```\n1. Run flag_debt_scanner.py --repo . --max-age-days 90 > debt.md\n2. For each flagged item:\n   a. Confirm it reached 100% (or was killed)\n   b. Find the issue\u002FPR that introduced it; verify owner agrees to remove\n   c. Delete dead branches; remove flag config\n   d. Run kill_switch_audit.py — should now show one fewer flag\n3. Update CHANGELOG: \"Removed N stale flags\"\n```\n\n### Workflow 3: Choose a provider\n\n```\n1. Estimate flag count (current + 12-month projection)\n2. Required features:\n   - Targeting rules (user, account, geo, %)?\n   - A\u002FB testing + stats?\n   - Audit log \u002F SOC2?\n   - Self-hosting \u002F data residency?\n3. Pricing budget (MAU * cost-per-MAU)\n4. See provider_comparison.md decision tree\n5. Build a 30-day proof-of-concept before signing\n```\n\n### Workflow 4: Design a kill switch\n\n```\n1. Identify the failure modes:\n   - Latency spike (which threshold?)\n   - Error rate spike (which threshold?)\n   - Business metric regression (which threshold?)\n2. Wire each to an abort:\n   - Manual: dashboard link + on-call playbook\n   - Automated: alert threshold flips flag back to 0%\n3. Test the kill switch in staging BEFORE production rollout\n4. Document in flag-doc; pass kill_switch_audit.py\n```\n\n## References\n\n- `references\u002Fflag_taxonomy.md` — 4 types, decision tree, ownership, lifespan\n- `references\u002Fprovider_comparison.md` — LaunchDarkly \u002F GrowthBook \u002F Statsig \u002F Unleash \u002F Flipt \u002F DIY trade-offs\n- `references\u002Frollout_strategies.md` — ring \u002F linear \u002F log \u002F cohort \u002F geo, abort criteria, monitoring\n- `references\u002Fflag_lifecycle.md` — request → design → ship → ramp → cleanup → archive\n\n## Slash command\n\n`\u002Fflag-cleanup` — Run the full cleanup workflow on the current repo: scan for debt, generate a removal plan, audit kill switches.\n\n## Asset templates\n\n- `assets\u002Fflag_request_template.md` — fill-in form for new flag requests (name, owner, type, kill switch, rollout plan)\n\n## Anti-patterns\n\n- **Permanent flag with `if (FLAG_FOO)` 50 places** — should be a Permission flag with a runtime config, not a Release flag\n- **Flag with no owner** — when the original engineer leaves, no one cleans it up\n- **No kill switch documented** — when the feature breaks, no one knows how to disable it\n- **A\u002FB test that ran 6 months** — pick a winner; running indefinitely is debt\n- **Flags as feature toggles for cosmetic changes** — ship via deploy, not flag\n\n## Verifiable success\n\nA team using this skill should achieve:\n- 100% of new flags pass `kill_switch_audit.py` at merge time\n- `flag_debt_scanner.py --max-age-days 90` returns ≤5 stale flags repo-wide\n- Every flag has a documented owner, type, and kill switch\n- Mean time to retire a Release flag: \u003C60 days from 100% rollout\n",{"name":5,"tags":24,"author":35,"context":36,"license":15,"version":37,"description":7,"compatible_tools":38},[25,26,27,28,29,30,31,32,33,34],"feature-flags","progressive-delivery","rollout","kill-switch","launchdarkly","growthbook","statsig","unleash","flipt","release-engineering","claude-code-skills","fork","2.9.0",[39,40,41,42,43,44],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add MHassan0000\u002FSkills --skill feature-flags-architect",{"tool":60,"command":61},"bunx","bunx skills add MHassan0000\u002FSkills --skill feature-flags-architect",{"tool":63,"command":64},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill feature-flags-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect\u002FSKILL.md",true,[68,74,80,84,88,92,98,102],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002Fflag_request_template.md","ASSET","资产文件",1770,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect\u002Fassets\u002Fflag_request_template.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fflag_lifecycle.md","REFERENCE","参考文档",5869,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect\u002Freferences\u002Fflag_lifecycle.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fflag_taxonomy.md",4511,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect\u002Freferences\u002Fflag_taxonomy.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fprovider_comparison.md",5148,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect\u002Freferences\u002Fprovider_comparison.md",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Frollout_strategies.md",5024,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect\u002Freferences\u002Frollout_strategies.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fflag_debt_scanner.py","SCRIPT","脚本",4827,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect\u002Fscripts\u002Fflag_debt_scanner.py",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fkill_switch_audit.py",5000,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect\u002Fscripts\u002Fkill_switch_audit.py",{"path":103,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Frollout_planner.py",4533,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fengineering\u002Ffeature-flags-architect\u002Fskills\u002Ffeature-flags-architect\u002Fscripts\u002Frollout_planner.py",[107,114,121,128,137,145],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":132,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":132,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":132,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]