Repository navigation
skills: split vercel-flags out of flags-sdk - #555
Draft
vincent-derks wants to merge 4 commits into
Draft
vincent-derks wants to merge 4 commits into
vincent-derks wants to merge 4 commits into
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.
Installing without --skill opens an interactive picker now that the repo has two skills. The SDK docs keep installing flags-sdk; the Vercel provider page adds vercel-flags.
Fast path to flags-sdk when the SDK is already installed, third-party rollouts stay in that provider, override is the one CLI command that needs FLAGS_SECRET, and skill install references use the existing @ form.
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
1 participant
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 the single
flags-sdkskill into two skills with clearly separated responsibilities.Why
Agents pick a skill from its name and description. One description cannot match both "roll this out to 10% of users" (planning, any stack) and "wire
vercelAdapterwith precompute" (SDK implementation). #554 pushedflags-sdktoward planning, which also pulled Vercel-specific guidance into a skill that is meant to be provider-flexible.What
skills/vercel-flags: entry point for any feature-flag intent in any stack. Owns choosing an integration (Flags SDK,@vercel/flags-core, OpenFeature), planning a flag, thevercel flagsCLI, project targeting, credentials, Flags Explorer overrides, and the@vercel/flags-coreexample for other frameworks. Hands Next.js and SvelteKit code work toflags-sdk.references/cli.mdholds the CLI mapping and lifecycle/safety checklist moved fromflags-sdk/references/providers.md.skills/flags-sdk: implementation only. Tighter description, "Choose an approach" and "CLI-only flag management" removed, the "Vercel Flags" section reduced to what the adapter does, the Express example replaced by a pointer. Points tovercel-flagsfor planning and management while staying usable on its own.flags-sdkonly (npx skills add vercel/flagswithout--skillopens an interactive picker now that the repo has two skills). The Vercel provider page installs both skills with explicit--skillflags. The Vercel Flags docs on vercel.com do the reverse in a follow-up.The descriptions still both match "add a feature flag to my Next.js app" on purpose: creating the flag on Vercel is
vercel-flagswork and declaring it isflags-sdkwork.vercel-flagsroutes straight toflags-sdkwhenflagsis already inpackage.json, so the extra hop only happens on a fresh project.Skill-to-skill install references use the
owner/repo@skillform already used forvercel/vercel@vercel-cliand on the homepage; the.mdxdocs keep their existing--skillform.Downstream consumers that vendor
flags-sdk(vercel-plugin, Vercel Agent) need a follow-up to pick upvercel-flagsand the narrowedflags-sdk, and to add a hand-off betweenvercel-flagsand thevercel-cliskill, whose description also claimsvercel flagsmanagement. Until then, an install with the oldflags-sdkplus the newvercel-flagshas two skills claiming the CLI.Validation
node scripts/validate-skills.mjs: both skills valid (descriptions 736 and 745 chars).@vercel/flags-coresnippet checked againstcreateRawClient.evaluate(flagKey, defaultValue?, entities?).