From vercel-shop
Plans which Vercel Shop template updates to roll into an existing project by analyzing scaffold metadata, rollout log, and current state. Outputs categorized recommendations with next steps.
npx claudepluginhub vercel/shop --plugin vercel-shop# Plan a Vercel Shop upgrade Use this command in an existing Vercel Shop project when the user wants to know which template updates are worth carrying forward into a customized storefront. ## Read these inputs 1. `.vercel-shop/bootstrap.json` in the project root if it exists 2. `template-version.json` from this plugin 3. every markdown entry in `template-rollout-log/` from this plugin except `README.md` 4. `AGENTS.md` 5. `.claude/settings.json` if present 6. the current project structure and any obviously relevant files mentioned by matching rollout entries ## Core rule Do not treat th...
/upgrade-deep-diveAnalyzes a specific upgrade with deep-dive report: risk assessment, numbered implementation steps, affected files, test strategy, rollback plan, code previews.
/harness-upgradeDiffs your HARNESS.md against the latest plugin template to discover new constraints, GC rules, and sections; presents them for review and selectively adopts updates.
/just-ship-updateUpdates CLAUDE.md and project.json against current framework templates, adding missing sections and fields while preserving project-specific content.
/marketplaceDiscovers and installs Vercel Marketplace integrations like databases, CMS, auth, and monitoring with guided setup, env verification, and local health checks.
/migrationPlans and executes design system migrations: audits tokens, generates codemods, manages deprecations, communicates changes, and creates rollback strategies.
/configuratorInitialize, validate, edit interactively, and review Saleor config.yml with schema checks, reference integrity, best practices, and mistake detection.
Share bugs, ideas, or general feedback.
Use this command in an existing Vercel Shop project when the user wants to know which template updates are worth carrying forward into a customized storefront.
.vercel-shop/bootstrap.json in the project root if it existstemplate-version.json from this plugintemplate-rollout-log/ from this plugin except README.mdAGENTS.md.claude/settings.json if presentDo not treat the template version as a complete migration plan. Use the rollout log to reason about individual changes because downstream projects may intentionally adopt only some of them. If bootstrap metadata includes scaffoldedAt, use that timestamp as the primary hint for which rollout entries are likely new to the project.
scaffoldedAt.scaffoldedAt, file dates, or version hints, plus any older entries that still look applicable from the current project state.Return a concise upgrade plan with:
Adopt now entriesReview manually entriesAlready present entriesNot applicable entries.vercel-shop/bootstrap.json is missing, say the project predates bootstrap metadata and continue with a best-effort audit.