Repository navigation
skills: split vercel-flags out of flags-sdk - #555
Merged
Merged
Conversation
flags-sdk now covers only Flags SDK implementation in Next.js and SvelteKit. The new vercel-flags skill owns planning, choosing an integration, the vercel flags CLI, credentials, and the flag lifecycle, and hands code work to flags-sdk.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Docs install both skills, the flags-core example lives only in vercel-flags, and the provider bullet states its stack condition.
feugy
approved these changes
Oct 16, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Splits
flags-sdkinto two skills. Agents pick a skill by its description, and one description cannot cover both "roll this out to 10%" and "wirevercelAdapterwith precompute". #554 pushed the SDK skill toward planning, which also pulled Vercel-specific guidance into a provider-neutral skill.What
skills/vercel-flags: stack-agnostic entry point. Planning, choosing an integration (Flags SDK /@vercel/flags-core/ OpenFeature), thevercel flagsCLI, credentials, lifecycle and safety checks. Hands Next.js and SvelteKit code toflags-sdk.skills/flags-sdk: implementation only. CLI management, "Choose an approach", and the Express example move out; pointers tovercel-flagsstay so it works standalone.flags-sdk; the Vercel provider page installs both with explicit--skillflags (no--skillopens an interactive picker now that the repo has two skills)."Add a flag to my Next.js app" matches both descriptions on purpose;
vercel-flagsroutes straight toflags-sdkwhenflagsis already inpackage.json.Follow-ups: re-vendor into vercel-plugin and Vercel Agent, add a
vercel-clihand-off, update vercel.com docs (vercel/front#90990).Validation:
validate-skillspasses, all relative links and docs URLs resolve, the@vercel/flags-coresnippet matchesevaluate(flagKey, defaultValue?, entities?).