Docs: Add FAQ about sharing config in monorepos for CSF Next

[kasperpeulen]

Closes #33616

What I did

Added a note after the automigrate command explaining that in monorepos with multiple Storybook configs, you need to run the command with the -c flag pointing to each config directory.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

This is a documentation-only change. Manual testing:

1. View the rendered MDX in the docs site
2. Verify the callout appears directly after the automigrate command

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that doesn't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>

Summary by CodeRabbit

• Documentation
  • Added monorepo guidance to CSF Next automigration docs, showing how to run the automigration with a config-directory flag for each config and including dedicated command snippets.
  • Included example command blocks demonstrating automigration across multiple Storybook configs using npm, pnpm, and yarn. Duplicate guidance appears in two relevant sections for discoverability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 12b492c

Command	Status	Duration	Result
nx run-many -t compile,check,knip,test,pretty-d...	✅ Succeeded	5m 27s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-01-28 14:58:43 UTC

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds monorepo guidance and a snippet showing how to run storybook automigrate csf-factories -c <config-dir> for each config directory; guidance and examples were inserted into docs/api/csf/csf-next.mdx (duplicated in two places) and a new snippet file was added. No code or data-structure changes.

Changes

Cohort / File(s)	Summary
Documentation - CSF Next docs/api/csf/csf-next.mdx	Inserted an informational monorepo Callout around the automigrate/upgrade text advising automigrate -c per config directory; the guidance appears in two locations (duplicated).
Snippets - Automigrate examples docs/_snippets/csf-factories-automigrate-with-config-directory.md	Added shell examples for running storybook automigrate csf-factories -c against two config dirs, with npm/pnpm/yarn variants.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• CLI: Make relative imports default in csf-factories codemod #32610 — Updated codemod messaging and doc links that point to the CSF Next docs modified here.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[kylegach]

Thanks, @kasperpeulen! Looks great!