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 · all subjects

ai/documentation

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

Document component purpose, usage, and APIs for AI agents

AI agents depend on how well components are documented. Key aspects worth documenting include purpose, usage, and APIs. JSDoc comments in code will be automatically extracted and included in the generated manifest for the agent.

Component JSDoc summary and description structure

Provide a JSDoc comment above component exports with a description explaining what the component should be used for, and optionally a @summary tag. The agent will receive the summary if present, or a truncated version of the description. Markdown syntax is supported for formatting and links.

Story summary and description for usage examples

Provide descriptions and optional summaries for each story, which serve as usage examples for the agent. Describe why you would use what is demonstrated, not just what is demonstrated. The agent receives the summary if present, or the first 60 characters of the description.

Provide prop descriptions in JSDoc comments

Add descriptions for component props in JSDoc comments within component code. Agents use these descriptions to understand how to use components effectively.

Unattached MDX docs pages can have summary in Meta tag

For unattached MDX docs pages such as design token or guideline documentation, provide a summary in the Meta tag, which will be included in the manifest and provided to the agent.

Include relevant details directly in MDX files for manifest

To ensure agents have access to necessary information, include relevant details directly in MDX files rather than referencing external sources. Relying on imports or dynamic rendering means that information will not be included in the manifest.

Storybook MCP server documentation structure

The Storybook MCP server documentation consists of three main sections: Overview (how the MCP server works, installation and configuration, and a typical workflow walkthrough), API (reference documentation for addon configuration options and MCP server tools), and Sharing (instructions for publishing or self-hosting the MCP server for team or community use).

Past Storybook versions documentation: 5.3 and 5.0 available

Documentation for Storybook versions 5.3 and 5.0 is available to help with migration from older versions. These are important milestones. For earlier versions, check specific releases in the monorepo.

Give your agent this brain