Add Feature Flags

[tech-and-finance]

https://github.com/tech-and-finance/awesome-feature-flags#readme

A curated list of feature flag and feature toggle tools, services, SDKs, and resources for progressive delivery. The list covers managed SaaS platforms (LaunchDarkly, Statsig, Split, ConfigCat, …), open-source self-hosted options (Unleash, Flagsmith, GrowthBook, Flipt, FeatBit, …), the OpenFeature vendor-neutral standard, and language-specific libraries across 12 ecosystems (JavaScript, Go, Python, Java, .NET, Ruby, PHP, Rust, Elixir, Swift, Kotlin, Flutter).

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

• Fully AI-generated pull requests are not accepted.
• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 4 other open pull requests. (Will complete and comment with links before requesting merge.)
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List.
• Your entry here should include a short description of the project/theme of the list. It should not describe the list itself.
• Your entry should be added at the bottom of the appropriate category. (Placed in Miscellaneous right after Continuous Integration and Continuous Delivery, the closest topical neighbor.)
• The title of your entry should be title-cased and the URL to your list should end in #readme.
• No blockchain-related lists.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days. (Created 2026-04-13, exactly 30 days as of submission.)
• Is not AI-generated.
• Run awesome-lint on your list and fix the reported issues. (Clean, 0 errors.)
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme.
• It's the result of hard work and the best I could possibly produce.
• The repo name of your list should be in lowercase slug format: awesome-feature-flags.
• The heading title of your list should be in title case format: # Awesome Feature Flags.
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. (Plus devops, feature-flags, feature-toggles, progressive-delivery.)
• Not a duplicate. Searched the existing awesome readme — no feature-flag list exists.
• Only has awesome items.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs.
• Entries have a description.
• Includes the Awesome badge.
• Has a Table of Contents section named Contents.
• Has an appropriate license. (CC0-1.0.)
• Has contribution guidelines in contributing.md.
• Has consistent formatting and proper spelling/grammar.

[tech-and-finance]

unicorn

[tech-and-finance]

Completed the 4 PR reviews per the guideline:

• Add CKEditor #4107 Add CKEditor
• Add ai-skill to CLI AI tools #4115 Add ai-skill to CLI AI tools
• Add Free LLM APIs #4110 Add Free LLM APIs
• Add Deception #4127 Add Deception