new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Storybook · Writing and testing · all subjects

test runner & ci

6 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Run Storybook CLI commands with require_escalated in sandboxed environments

In sandboxed Codex environments, run every Storybook CLI command with the require_escalated flag to avoid network and port restriction failures that could cause confusing failures like the dev server being unable to find a free port to bind to.

Run Storybook CLI from the same working directory as dev server

Run the Storybook dev server and every storybook ai command from the same working directory: the package where Storybook is installed. In a monorepo, this is often a leaf package such as packages/ui.

Use STORYBOOK_FEATURE_AI_CLI environment variable for AI CLI

When running storybook ai commands, prepend STORYBOOK_FEATURE_AI_CLI=1 to access the AI CLI feature. For example: STORYBOOK_FEATURE_AI_CLI=1 npx storybook ai --help

Read command-specific help for storybook ai subcommands

Before invoking any storybook ai command for the first time in a session, run STORYBOOK_FEATURE_AI_CLI=1 npx storybook ai <command> --help and read it fully. The top-level help only lists the commands; each command's payload shape and usage rules live in its own help output. Never guess a --json payload from the command name.

Reuse existing Storybook dev server instead of starting a new one

When a dev server already serves the project's Storybook (typically at http://localhost:6006), reuse it instead of starting a second one. Otherwise, start one in the background using the project's preferred package manager and existing package.json Storybook script (e.g., npm run storybook). Wait until the URL responds before running commands that need it.

Leave dev server running after work is complete

The Storybook dev server is part of the deliverable, not a temporary verification tool. Leave it running when work is done so the user can continue browsing stories. Never kill it after verification.

Give your agent this brain