// Plan and execute migration from Mercur 1.x to 2.0. Classifies project difficulty, reads relevant migration docs, and follows stop conditions.
| name | migration-guide |
| description | Plan and execute migration from Mercur 1.x to 2.0. Classifies project difficulty, reads relevant migration docs, and follows stop conditions. |
| argument-hint | [path-to-old-project] |
Use this skill when:
Before any action, read:
docs/migrations/mercur-1.x-to-2.0/README.md — entry point, version check, package/directory mapping, approachRead references/decision-tree.md in this skill directory, then:
package.json — note @mercurjs/b2c-core version to determine 1.x versionapps/admin/) — search there when scanning for custom dashboard pagesBased on classification, read from docs/migrations/mercur-1.x-to-2.0/:
| Document | Starter | Light Custom | Heavy Custom |
|---|---|---|---|
| README.md | Required | Required | Required |
| dashboards.md | Skim | Required | Required |
medusa-config.ts (plugins, modules, providers)bunx @mercurjs/cli@latest add <block>)Stop and ask the user when:
@mercurjs/core.migration/ or any private test directoriesReview code changes for contract compliance, type safety, and regression risk. Use after completing any non-trivial implementation, before merging PRs, or when asked to review code quality across any mercur package.
Analyze a Mercur 1.x project and guide migration to 2.0. Self-contained — works without access to the mercur monorepo.
Enforce correct form UI patterns when creating or modifying forms in packages/admin. Use when writing form fields, edit drawers, create modals, or any form-based UI in the admin package. Covers Form.Field pattern, labels, errors, hints, grids, submit guards, drawer/modal structure.
Enforce correct page and section UI patterns when creating or modifying admin pages. Use when building list pages, detail pages, Container sections, action menus, empty states, delete flows, or any page-level UI in packages/admin.
Enforce correct tab UI patterns when creating custom tabs for TabbedForm wizards in packages/admin. Use when adding new tabs to product create, price list create, or any multi-step form wizard. Covers defineTabMeta, layout, heading levels, section structure, i18n.
Review admin UI code for consistency with established patterns. Use after writing any UI code in packages/admin to catch anti-patterns — wrong form components, hardcoded strings, missing i18n, incorrect heading levels, manual error rendering, missing data-testid, raw Controller usage.