Code
How storybookjs/storybook is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely public API
- Likely public API
- Likely start-up file
- Likely start-up file
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd a new addon
- Create addon package directory under code/addons/{addon-name} with package.json following the pattern of code/addons/a11y/package.json
- Create manager UI entry point at code/addons/{addon-name}/manager.js (see a11y addon example)
- Create build-config.ts following the builder pattern seen in code/addons/a11y/build-config.ts
- Add corresponding E2E tests in code/e2e-sandbox/addon-{addon-name}.spec.ts following existing addon test patterns
Add a new framework integration
- Create framework package under code/frameworks/{framework-name} with build-config.ts and build-schema.json
- Define the builder configuration in build-schema.json (see Angular Vite example)
- Create builders.json for framework-specific builder registration
- Add test storybook under test-storybooks/{framework-name} with sample stories and package.json
Add a new renderer
- Create renderer package under code/renderers/{framework} with package.json and README.md
- Implement renderer entry points and build configuration in build-config.ts
- Add E2E tests in code/e2e-sandbox to verify renderer integration with core
Change the public API
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.