メニュー
Upgrades a project to a new major version of Vibe (@vibe/core) using MCP migration tools. Use when upgrading from v2 to v3 (monday-ui-react-core → @vibe/core) or from v3 to v4.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | vibe-upgrade |
| description | Upgrades a project to a new major version of Vibe (@vibe/core) using MCP migration tools. Use when upgrading from v2 to v3 (monday-ui-react-core → @vibe/core) or from v3 to v4. |
| argument-hint | [project-path] |
| user-invocable | true |
| allowed-tools | ["Read","Glob","Grep","Bash","Edit","mcp__vibe__v3-migration","mcp__vibe__v4-migration"] |
Do NOT attempt to:
The Vibe MCP migration tools have authoritative, version-specific knowledge of every breaking change. They are the only reliable way to perform this migration correctly.
If $ARGUMENTS is provided, use it as the project path. Otherwise use the current working directory. In a monorepo, use the path to the specific workspace package that uses @vibe/core, not the repo root.
Read <project-path>/package.json to find the installed version:
"@vibe/core": "^3.12.0"
Or for v2:
"monday-ui-react-core": "^2.x.x"
Select the MCP tool based on current major version:
| Current | Target | MCP Tool |
|---|---|---|
v2.x (monday-ui-react-core) | v3 (@vibe/core) | mcp__vibe__v3-migration |
v3.x (@vibe/core) | v4 | mcp__vibe__v4-migration |
If neither monday-ui-react-core nor @vibe/core is in package.json: Stop and inform the user this skill does not apply.
If the version is outside the table above (e.g., v1.x or already v4): Stop and inform the user that no MCP migration tool exists for that version path.
If migrating v2 → v4 (two hops): Complete the v2→v3 migration in full (all 5 steps), then restart from Step 1 for the v3→v4 migration.
Call the appropriate tool with the absolute project path:
# For v3 → v4:
mcp__vibe__v4-migration({ projectPath: "/absolute/path/to/project" })
# For v2 → v3:
mcp__vibe__v3-migration({ projectPath: "/absolute/path/to/project" })
The tool returns:
Wait for the tool to complete before touching any files.
If the tool fails or returns an error: stop, report the error to the user, and do not attempt a manual migration.
For each file in the tool output:
Rules:
Run the install command provided by the MCP tool output. It will include the correct package version.
For v2 → v3 only: after running the install command, also remove the v2 package:
| Package Manager | Uninstall Command |
|---|---|
npm | npm uninstall monday-ui-react-core |
yarn | yarn remove monday-ui-react-core |
pnpm | pnpm remove monday-ui-react-core |
Do not rely on the MCP tool to include this step — always run it explicitly for v2→v3 migrations.
Detect the project's package manager from lock files first:
| Lock File | Package Manager |
|---|---|
yarn.lock | yarn |
pnpm-lock.yaml | pnpm |
package-lock.json | npm |
# Example (use the exact command from the tool output):
npm install @vibe/core@4
Run build and tests:
# Yarn:
yarn build && yarn test
# npm:
npm run build && npm test
Use the Grep tool to confirm any deprecated patterns flagged by the MCP tool are gone. Report any remaining issues to the user.
| Mistake | Correct Behavior |
|---|---|
| Skipping the MCP tool and using training knowledge | Always run the MCP tool first |
| Only applying changes to some files | Apply ALL changes from the tool output |
| Calling the MCP tool with a relative path | Always use an absolute path |
| Running v2→v4 in one hop | Complete v2→v3 fully, then run v3→v4 |
Skipping monday-ui-react-core uninstall on v2→v3 | Always explicitly uninstall the v2 package |
| Continuing after a tool error | Stop and report; never attempt manual migration |
| Using wrong package manager | Detect from lock files before running install |
@vibe/coreOnce the migration is complete, use /vibe-best-practices to verify that all components in the upgraded project follow the current Vibe standards — particularly:
/next version available@vibe/iconsMigrate an existing monday.com app from the old OAuth flow to the new OAuth 2.1 flow. Changes token endpoint from oauth2/token to oauth_ms/oauth/token, adds refresh token support, updates token storage, and optionally adds PKCE. ALWAYS use when someone mentions migrating monday OAuth, switching to the new OAuth flow, adding refresh tokens, updating the monday token endpoint, token expiration, or when code calls auth.monday.com/oauth2/token. Also trigger on OAuth deadline/deprecation announcements. Do NOT use for new OAuth from scratch, non-monday OAuth (Google, Slack, Spotify), client credentials flow, DCR, or general monday debugging.
Ensures Vibe design system (@vibe/core) components follow best practices and accessibility standards. Use when writing or reviewing UI code in monday.com apps that import from @vibe/core or @vibe/core/next.
Build, test, and debug monday.com GraphQL queries and mutations. Introspects the live schema, handles pagination, column value formatting, and validates queries by executing them. Use when writing API queries, debugging response shapes, or figuring out column value JSON formats.
Bootstrap a project using the monday.com public GraphQL API. Installs the @mondaydotcomorg/api SDK, configures auth, pins API version, and sets up TypeScript codegen. Use when starting a new API integration or adding monday.com API to an existing project.
Migrate between monday.com API versions. Identifies your current version, shows breaking changes, guides code updates, and tests migrated queries. Use when a new API version is released or you need to upgrade from a deprecated version.
Production operations guidance for the monday.com API. Covers error handling, rate limits, complexity budgeting, retry strategies, webhooks, and caching. Use when preparing an API integration for production or debugging production issues.