Storybook Testing
yonatangross/orchestkit
Storybook 10 testing patterns with Vitest integration, ESM-only distribution, CSF3 typesafe factories, play() interaction tests, Chromatic TurboSnap visual regression, module automocking…
A skill your agent uses when writing a Storybook story for a component gated on a feature flag — boolean flags or multivariate/experiment-arm variants.
Install Setting Feature Flags In Storybook
$ npx skills add PostHog/posthog --skill setting-feature-flags-in-storybook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog setting-feature-flags-in-storybook --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/setting-feature-flags-in-storybook .claude/skills/setting-feature-flags-in-storybook && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "setting-feature-flags-in-storybook" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/setting-feature-flags-in-storybook into .claude/skills/setting-feature-flags-in-storybook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-feature-flags-in-storybook", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog/tree/master/.agents/skills/setting-feature-flags-in-storybookType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog --skill setting-feature-flags-in-storybook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog setting-feature-flags-in-storybook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/setting-feature-flags-in-storybook .agents/skills/setting-feature-flags-in-storybook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "setting-feature-flags-in-storybook" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/setting-feature-flags-in-storybook into .agents/skills/setting-feature-flags-in-storybook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-feature-flags-in-storybook", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill setting-feature-flags-in-storybook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog setting-feature-flags-in-storybook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/setting-feature-flags-in-storybook .cursor/skills/setting-feature-flags-in-storybook && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "setting-feature-flags-in-storybook" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/setting-feature-flags-in-storybook into .cursor/skills/setting-feature-flags-in-storybook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-feature-flags-in-storybook", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog.git --path .agents/skills/setting-feature-flags-in-storybook--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog --skill setting-feature-flags-in-storybook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog setting-feature-flags-in-storybook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/setting-feature-flags-in-storybook .gemini/skills/setting-feature-flags-in-storybook && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "setting-feature-flags-in-storybook" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/setting-feature-flags-in-storybook into .gemini/skills/setting-feature-flags-in-storybook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-feature-flags-in-storybook", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog setting-feature-flags-in-storybookInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog --skill setting-feature-flags-in-storybook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/setting-feature-flags-in-storybook .github/skills/setting-feature-flags-in-storybook && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "setting-feature-flags-in-storybook" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/setting-feature-flags-in-storybook into .github/skills/setting-feature-flags-in-storybook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-feature-flags-in-storybook", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill setting-feature-flags-in-storybook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog setting-feature-flags-in-storybook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/setting-feature-flags-in-storybook .opencode/skills/setting-feature-flags-in-storybook && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "setting-feature-flags-in-storybook" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/setting-feature-flags-in-storybook into .opencode/skills/setting-feature-flags-in-storybook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-feature-flags-in-storybook", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
setting-feature-flags-in-storybook- GitHub stars
- 40k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 482 words
- Files
- 1
- Skills in repo
- 254
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when writing a Storybook story for a component gated on a feature flag — boolean flags or multivariate/experiment-arm variants.
- Writing a Storybook story for a component gated on a feature flag — boolean flags
- SKILL.md covers How to use it, Why the obvious approach fails, Under the hood (implementation… and See also
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Multivariate/experiment-arm variants
What it does
Setting Feature Flags In Storybook is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Use when writing a Storybook story for a component gated on a feature flag — boolean flags or multivariate/experiment-arm variants. Covers the featureFlags story parameter and why imperatively setting flags renders the flag-off branch in visual-regression snapshots while passing in jest.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Unit testing and Visual regression testing. It works with Storybook, Jest and PostHog. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…
When your agent uses it
- Writing a Storybook story for a component gated on a feature flag — boolean flags
- Multivariate/experiment-arm variants
Example prompts
- “/setting-feature-flags-in-storybook”
What it can do on your machine
Read from SKILL.md and the folder at commit c012c8d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Setting Feature Flags In Storybook loads about 1.1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 482 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 482 words (~1,119 tokens).
“Mental model: boolean flags always work (they ride the always-merged baseline); variant values need a gate that only the featureFlags parameter opens correctly.”
- name
- setting-feature-flags-in-storybook
Files
Just SKILL.md in .agents/skills/setting-feature-flags-in-storybook of PostHog/posthog.
Open the folder on GitHubat commit c012c8d
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Setting Feature Flags In Storybook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Setting Feature Flags In Storybook this skillPostHog/posthog | 40k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Storybook Testingyonatangross/orchestkit | 292 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.2k | Automated safety check: Pass | None | |
| Testingradix-ng/primitives | 274 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Test Specialisttravisjneuman/.claude | 100 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Sanity Visual Regressionsanity-io/sanity | 6.4k | — | ~3.4k | Automated safety check: Pass | MIT |
Similar skills
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
Testing
radix-ng/primitives
Test Radix NG primitives across every layer and pick the RIGHT one for a change: Vitest unit (zoneless), jest-axe a11y, Playwright browser regression (apps/visual-regression), SSR…
Test Specialist
travisjneuman/.claude
Test-writing patterns for JS/TS, Python, Go, and Rust (unit, integration, E2E, visual regression).
- Official
Sanity Visual Regression
sanity-io/sanity
Add, review, and maintain Chromatic visual regression coverage in the Sanity monorepo via dev/storybook stories, the vitest browser-mode suite, and Playwright e2e snapshots.
Test Commander
EliasOulkadi/shokunin
Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration).
More from PostHog/posthog
All 254 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Categories
Questions about Setting Feature Flags In Storybook
What does Setting Feature Flags In Storybook do?
A skill your agent uses when writing a Storybook story for a component gated on a feature flag — boolean flags or multivariate/experiment-arm variants. Setting Feature Flags In Storybook is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Use when writing a Storybook story for a component gated on a feature flag — boolean flags or multivariate/experiment-arm variants.
When should I use Setting Feature Flags In Storybook?
Setting Feature Flags In Storybook fits situations like: writing a Storybook story for a component gated on a feature flag — boolean flags; multivariate/experiment-arm variants.
How do I install Setting Feature Flags In Storybook in Claude Code?
Run `npx skills add PostHog/posthog --skill setting-feature-flags-in-storybook -a claude-code`. Or copy the skill folder (.agents/skills/setting-feature-flags-in-storybook in PostHog/posthog) into .claude/skills/setting-feature-flags-in-storybook in your project. Claude Code loads it when a task matches its description.
How do I install Setting Feature Flags In Storybook in Codex?
Run `npx skills add PostHog/posthog --skill setting-feature-flags-in-storybook -a codex`. Or copy the skill folder (.agents/skills/setting-feature-flags-in-storybook in PostHog/posthog) into .agents/skills/setting-feature-flags-in-storybook in your project. Codex loads it when a task matches its description.
Can I use Setting Feature Flags In Storybook in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill setting-feature-flags-in-storybook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setting-feature-flags-in-storybook, .gemini/skills/setting-feature-flags-in-storybook, .github/skills/setting-feature-flags-in-storybook and .opencode/skills/setting-feature-flags-in-storybook in your project.
What does Setting Feature Flags In Storybook need to run?
SKILL.md names no scripts, command-line tools or credentials: Setting Feature Flags In Storybook is instructions for the agent only.
Does Setting Feature Flags In Storybook access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Setting Feature Flags In Storybook safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Setting Feature Flags In Storybook use?
Setting Feature Flags In Storybook has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Setting Feature Flags In Storybook use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Setting Feature Flags In Storybook?
Skills that share tags, products or a category with Setting Feature Flags In Storybook: Storybook Testing (yonatangross/orchestkit, 292 stars), Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars), Testing (radix-ng/primitives, 274 stars) and Test Specialist (travisjneuman/.claude, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Setting Feature Flags In Storybook?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,209 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 10, 2026.
Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.