Discovered, not connected
There is nothing to connect. Storybook is found in the repositories you already selected: the configuration, the story files, and the relationship between a story and the component it exercises. No separate account, no hosted instance, no build step, no deployed Storybook required.
This matters because plenty of teams have a Storybook that runs locally and is never published anywhere. For readiness purposes that is still valuable evidence, and a tool that only reads published Storybooks would miss all of it.
What a story tells Onefold
- That the component exists
- A story is the strongest discoverability signal there is. A component with a story is one an agent can find, name and see used correctly.
- Which props are real
- Args and controls show which props are actually meant to be set, and with what values, which is often more honest than the type signature.
- What correct usage looks like
- Every story is a worked example. Examples are one of the eight readiness dimensions precisely because agents pattern match, and a story is the right pattern to match.
- Which states were considered
- Loading, empty, error and disabled stories say the states were thought about. Their absence is a finding on its own.
- What the docs say
- Docs pages and MDX attached to stories are read as documentation, and feed the semantics and constraints dimensions.
The cheapest readiness improvement there is
Across the dimensions Onefold scores, writing a story for an undocumented exported component moves more numbers per minute spent than anything else. One story raises discoverability, gives the component an example, and clarifies its API, without writing a word of prose.
If your report comes back with a list of components that have no stories, that list is usually the shortest path to a materially better score. Which is a strange thing for a product to tell you, except that the alternative is a score you cannot act on.
A story is not a substitute for guidance. Stories show what a component does. They do not say when to reach for something else, which is the gap agents fall into most often. Both dimensions are scored separately for exactly this reason.
Find out which components have no story
It comes back in the first report, alongside the rest of the inventory.
Request early access