Featurevisor skills for AI coding agents

The Featurevisor skill teaches your coding agent, such as Claude Code, Codex, Cursor or OpenCode, how Featurevisor projects work. With it, the agent writes definitions and specs, runs the CLI, and explains why a context gets a value. Its changes go through review like anyone else's.

What it can do#

Write features, global variables, segments and attributes, including rules and conditions
Write test specs, checks and scenarios, and run them
Answer questions such as what is enabled where, and why checkout is disabled for user-9
Start a new project, or work in one that uses sets and promotions
Wire features into an application with an SDK, React, Vue.js or an OpenFeature provider

Install the skill#

Install it through skills.sh:

Command

npx skills add featurevisor/featurevisor

It asks which agents to install the skill for, such as Claude Code, Codex, Cursor and OpenCode.

Update the skill#

From the project where you installed it, update only the Featurevisor skill:

Command

npx skills update featurevisor --project

For a global installation, use npx skills update featurevisor --global instead. The skills CLI also updates every installed skill when you leave out the skill name. Review any local changes before updating, and review the updated skill files and lockfile before committing them.

If an older installation lacks the source tracking needed for updates, repeat npx skills add featurevisor/featurevisor --skill featurevisor with the same agents and installation scope. Updating the skill does not upgrade your Featurevisor CLI or application SDKs. Check their versions before adopting new syntax.

Ask it#

Type /featurevisor in your agent's chat, followed by what you need, in plain words. You do not need to know the YAML to ask. A product manager or a support colleague can ask what a user gets and why, and any change the agent proposes still goes through review.

Write definitions#

/featurevisor create a wishlist feature starting at 5%

/featurevisor add an A/B test on the pricing page with control and treatment variations, 50/50, only in Germany and the Netherlands

/featurevisor create a checkoutSettings global variable with currency and paymentMethods (array), override paymentMethods to [card, ideal] for NL

/featurevisor create a segment for adult iPhone users in NL or DE who are not on the newsletter

/featurevisor make oneClickCheckout and expressShipping mutually exclusive experiments, 50/50

/featurevisor let the QA team see wishlist in production while it's still at 0% for everyone else

/featurevisor deprecate the oldCheckout feature with a two week grace period

Inspect and debug#

/featurevisor why is checkout disabled for user-9 in Germany?

/featurevisor explain the buyButton feature

/featurevisor list every feature enabled in production that has an A/B test running and no test spec

/featurevisor write tests for pricing covering both variations

/featurevisor find unused segments and attributes, plus any duplicate segments

/featurevisor simulate the 25% wishlist rollout against 10k users, will it actually hit 25%?

Set up and integrate#

/featurevisor set up a new Featurevisor project with staging and production environments, and web and mobile tags

/featurevisor wire the checkout feature into my React app, with the datafile refreshing every 5 minutes

/featurevisor set up the Featurevisor OpenFeature provider in our Node.js service, reusing our existing SDK instance

/featurevisor run our test specs through the Python SDK to confirm it evaluates the same as the browser

Source#

The skill is open source, in the Featurevisor repository.

Quick start, which uses the skill for its first feature
Documentation for LLMs