Release: Prerelease 10.3.0-alpha.18

.agents/skills/canary/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: canary
+description: Triggers a canary release for a Storybook PR. Use when the user wants to publish a canary version, create a pre-release, or test a PR via npm.
+allowed-tools: Bash
+---
+
+# Publish Canary Release
+
+Publishes a canary version of Storybook from a PR to npm.
+
+## Usage
+
+To trigger a canary release, run:
+
+```bash
+gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>
+```
+
+## What happens
+
+1. GitHub Actions builds and publishes the PR as `0.0.0-pr-<PR_NUMBER>-sha-<SHORT_SHA>`
+2. The version is published to npm with the `canary` tag
+3. The PR body is updated with the exact version and install instructions
+
+## Version format
+
+The canary version follows a **predictable structure**:
+
+```
+0.0.0-pr-<PR_NUMBER>-sha-<SHORT_SHA>
+```
+
+- `<PR_NUMBER>`: The PR number (e.g., `33526`)
+- `<SHORT_SHA>`: First 8 characters of the commit SHA (e.g., `a2e09fa2`)
+
+**Example:** For PR #33526 with commit `a2e09fa284a...`, the canary version is:
+`0.0.0-pr-33526-sha-a2e09fa2`
+
+You can construct the version yourself if you know the PR number and the latest commit SHA on that PR.
+
+## After publishing
+
+Check the PR body for the published version. It will show something like:
+
+> This pull request has been released as version `0.0.0-pr-33365-sha-b6656566`
+
+Then test with:
+
+```bash
+npx storybook@<VERSION_FROM_PR> sandbox
+```
+
+Or upgrade an existing project:
+
+```bash
+npx storybook@<VERSION_FROM_PR> upgrade
+```
+
+## Requirements
+
+- You must have admin permissions on the storybookjs/storybook repo
+- The PR must exist and be open
+- You need `gh` CLI authenticated
+
+## Monitor progress
+
+Watch the workflow run at:
+https://github.com/storybookjs/storybook/actions/workflows/publish.yml

.agents/skills/github-qa-labels/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: github-qa-labels
+description: Label GitHub issues and PRs found during QA testing. Use when organizing QA findings with proper labels.
+allowed-tools: Bash
+---
+
+# GitHub QA Labels
+
+When creating or organizing issues/PRs found during QA testing, apply these labels.
+
+## QA tracking label
+
+Add `upgrade:<version>` label to track all QA findings for a release:
+
+```bash
+# Create label if it doesn't exist
+gh label create "upgrade:10.2" --repo storybookjs/storybook --color "0E8A16" --description "Issues/PRs found during 10.2 upgrade QA"
+
+# Add to issue/PR
+gh issue edit <NUMBER> --repo storybookjs/storybook --add-label "upgrade:10.2"
+gh pr edit <NUMBER> --repo storybookjs/storybook --add-label "upgrade:10.2"
+```
+
+## Severity labels
+
+Add `sev:S1` through `sev:S4` to **bugs only** (not docs or feature requests):
+
+```bash
+gh issue edit <NUMBER> --repo storybookjs/storybook --add-label "sev:S2"
+```
+
+Severity levels:
+
+- **sev:S1**: Critical, blocking, no workaround
+- **sev:S2**: Significant issue, may have workaround
+- **sev:S3**: Moderate issue, workaround exists
+- **sev:S4**: Minor issue, edge case, easy workaround
+
+## What gets severity labels
+
+| Type                    | Severity label? |
+| ----------------------- | --------------- |
+| Bug (runtime error)     | Yes             |
+| Bug (type error)        | Yes             |
+| Bug (automigrate issue) | Yes             |
+| Documentation issue     | No              |
+| Feature request         | No              |
+| Enhancement             | No              |
+
+## Batch labeling
+
+Label multiple issues at once:
+
+```bash
+gh issue edit 33524 --repo storybookjs/storybook --add-label "upgrade:10.2" && \
+gh issue edit 33527 --repo storybookjs/storybook --add-label "upgrade:10.2" && \
+gh pr edit 33526 --repo storybookjs/storybook --add-label "upgrade:10.2"
+```

.agents/skills/pr/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: pr
+description: Creates a pull request following Storybook conventions. Use when creating PRs, opening pull requests, or submitting changes for review.
+allowed-tools: Bash, Read
+---
+
+# Create Pull Request
+
+Creates a PR following Storybook conventions.
+
+## Title format
+
+`[Area]: [Description]`
+
+- Area is capitalized, no spaces (dashes allowed)
+- Examples:
+  - `CSFFactories: Fix type export`
+  - `Nextjs-Vite: Add support`
+  - `CLI: Fix automigrate issue`
+
+## Labels
+
+Add these labels to the PR:
+
+**Category (required, pick one):**
+
+- `bug` - fixes incorrect behavior
+- `maintenance` - user-facing maintenance
+- `dependencies` - upgrading/downgrading deps
+- `build` - internal build/test updates (no changelog)
+- `cleanup` - minor cleanup (no changelog)
+- `documentation` - docs only (no changelog)
+- `feature request` - new feature
+- `BREAKING CHANGE` - breaks compatibility
+- `other` - doesn't fit above
+
+**CI (required, pick one):**
+
+- `ci:normal` - standard sandbox set; default for most code changes
+- `ci:merged` - merged sandbox set
+- `ci:daily` - daily sandbox set; use this when changes affect prerelease sandboxes or sandboxes pinned to a framework or React version other than latest
+- `ci:docs` - documentation-only changes (use with `documentation` category)
+
+## PR body
+
+Read `.github/PULL_REQUEST_TEMPLATE.md` from the repository root.
+
+Copy that template **EXACTLY**, including all HTML comments (`<!-- ... -->`). Fill in the relevant sections based on the changes, but keep all comments intact.
+
+## Command
+
+Always create PRs in draft mode:
+
+```bash
+gh pr create --draft --title "<Area>: <Description>" --body "<FILLED_TEMPLATE>" --label "<category>,<ci>"
+```

.agents/skills/storybook-upgrade/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: storybook-upgrade
+description: Upgrade Storybook to a specific version (canary or release). Use this when upgrading Storybook packages in an external app, reproduction, or test project.
+allowed-tools: Bash
+---
+
+# Storybook Upgrade
+
+Upgrades all Storybook packages in a project to a specific version.
+
+## Why this matters for the monorepo
+
+This skill is mainly for validating Storybook changes outside this repository.
+
+- QA a canary build from a Storybook PR in a downstream app
+- Reproduce or verify a bug in an external project
+
+## Usage
+
+```bash
+npx storybook@<VERSION> upgrade
+```
+
+## Examples
+
+### Upgrade to canary version
+
+```bash
+npx storybook@0.0.0-pr-33526-sha-a2e09fa2 upgrade
+```
+
+### Upgrade to latest stable
+
+```bash
+npx storybook@latest upgrade
+```
+
+### Upgrade to specific release
+
+```bash
+npx storybook@8.5.0 upgrade
+```
+
+## What it does
+
+1. Detects all `@storybook/*` packages in your project
+2. Upgrades them all to the specified version
+3. Handles peer dependencies automatically
+4. Works with npm, yarn, and pnpm
+
+## Important
+
+- **DO NOT** manually install storybook packages with `npm add` / `yarn add` / `pnpm add`
+- Always use `npx storybook@<version> upgrade` to ensure all packages stay in sync
+- The upgrade command handles version resolution across all storybook packages
+- **ALWAYS upgrade only 1 major version at a time!**
+  - Example: 8.x → 9.x → 10.x → canary of 10
+  - Never skip major versions (e.g., don't go from 8.x directly to 10.x)

.claude/skills/canary/SKILL.md

@@ -0,0 +1 @@
+@../../../.agents/skills/canary/SKILL.md

.claude/skills/github-qa-labels/SKILL.md

@@ -0,0 +1 @@
+@../../../.agents/skills/github-qa-labels/SKILL.md

.claude/skills/pr/SKILL.md

@@ -0,0 +1 @@
+@../../../.agents/skills/pr/SKILL.md

.claude/skills/storybook-upgrade/SKILL.md

@@ -0,0 +1 @@
+@../../../.agents/skills/storybook-upgrade/SKILL.md

.cursor/mcp.json

@@ -1,5 +1,12 @@
 {
   "mcpServers": {
+    "nx": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "nx-mcp@latest"
+      ]
+    },
     "wallaby": {
       "command": "node",
       "args": [