FeatureGate
Request access

FeatureGate skill suite

Install a Codex-first skill suite that helps coding agents integrate or migrate JavaScript and TypeScript apps to FeatureGate.

The FeatureGate skill suite gives a coding agent a focused playbook for integrating or migrating a JavaScript or TypeScript app to FeatureGate. It is repo-published and inspectable: the skill tells the agent how to choose the right SDK, preserve safe fallbacks, avoid credential mistakes, and leave a migration report for review.

Humans keep control of setup

The skill does not create FeatureGate projects, flags, runtime keys, client keys, or exposure settings by default. It produces exact setup steps for a human and keeps raw secrets out of the migration report.

Install

Copy the agent-skills/featuregate-integration directory from the FeatureGate repository into your agent's skill directory.

terminal
sh
mkdir -p .codex/skills
cp -R agent-skills/featuregate-integration .codex/skills/featuregate-integration

Then ask your agent to use the FeatureGate integration skill when it works on your app.

prompt
md
Use the FeatureGate integration skill.

Migrate this app's feature flag wrapper to FeatureGate.
Preserve existing defaults and tell me which FeatureGate project, environment,
flag keys, and runtime/client keys I need to create manually.

What it covers

SDK choice

Route server, browser, React, and OpenFeature integrations to the safest SDK path.

Migration strategy

Prefer wrapper-strangler migration over broad call-site rewrites.

Verification

Require tests, typechecks, assumptions, unsupported patterns, and manual setup steps.

SDK choice

The skill starts by inspecting your app instead of guessing. It looks for frameworks, runtime boundaries, existing feature-flag wrappers, OpenFeature usage, vendor SDKs, tests, and public/private environment variable conventions.

Use server SDKs for trusted decisions

Backend, SSR, worker, authorization, entitlement, billing, and data-access decisions should use @featuregate/server or the server OpenFeature provider with a secret server runtime key.

Use browser SDKs only for client-exposed UI flags

Browser and React paths use publishable client keys through @featuregate/browser, @featuregate/react, or the browser OpenFeature provider.

Use OpenFeature when the app already has OpenFeature

Existing OpenFeature call sites can usually stay in place while the provider registration moves to FeatureGate.

Migration strategy

For existing apps, the skill prefers the local wrapper or provider boundary. Instead of rewriting every vendor call at once, it changes the wrapper internals to FeatureGate, keeps the wrapper API stable, and records direct vendor call sites for later cleanup.

The first slice has deep guidance for:

  • native FeatureGate server, browser, and React SDKs
  • FeatureGate server and browser OpenFeature providers
  • OpenFeature migrations
  • LaunchDarkly-style JavaScript usage
  • generic wrapper assessment for other vendors or homegrown flag systems

Executable codemods, broad vendor matrices, non-JavaScript SDKs, and dual-read production parity workflows are future scope.

Verification

The skill should end with a migration report that includes:

  • SDK path chosen and why
  • changed files
  • existing wrapper or provider found
  • FeatureGate setup checklist for the human
  • tests, typecheck, build, or lint commands run
  • assumptions and unsupported patterns
  • confirmation that no raw keys, cookies, sessions, or management credentials were included
Pair with the SDK docs

The skill is docs-versioned with the SDK pages. When SDK public APIs, credential rules, or OpenFeature behavior change, update the skill suite in the same change.

Server TypeScript SDK

Evaluate typed flags locally from trusted server code.

Browser SDK

Evaluate client-exposed flags with publishable client keys.

React SDK

Use browser evaluation through React providers and hooks.

OpenFeature Provider

Use FeatureGate with OpenFeature-compatible server-side apps.