ワンクリックで
marketplace-deploy
// Deploys a Sitecore Marketplace app to Vercel with correct CSP headers and configuration.
// Deploys a Sitecore Marketplace app to Vercel with correct CSP headers and configuration.
Adds AI Skills integration (Brand Review API) to a Sitecore Marketplace app. Use when the user wants to add AI-powered content analysis, brand review, or brand compliance checking.
Adds a new extension point route to a Sitecore Marketplace app. Use when the user wants to add a custom field, dashboard widget, context panel, fullscreen page, or standalone route.
Adds XM Cloud API integration to a Sitecore Marketplace app. Use when the user wants to access Sites, Pages, Authoring, Content Transfer, Search, or Agent APIs from XM Cloud.
Builds UI components using the Blok design system for Sitecore Marketplace apps. Use when the user wants to create UI, add components, build a page layout, or work with Blok/shadcn components in a marketplace app.
Scaffolds a new Sitecore Marketplace app using the official SDK. Use when the user wants to create a new marketplace app, start a new Sitecore project, or initialize a marketplace integration.
Sitecore Marketplace SDK API reference. Use when the user asks about SDK methods, types, queries, mutations, subscriptions, or how to use any Sitecore Marketplace SDK API.
| name | marketplace-deploy |
| description | Deploys a Sitecore Marketplace app to Vercel with correct CSP headers and configuration. |
| disable-model-invocation | true |
You are helping the user deploy their Sitecore Marketplace app to Vercel.
Important: This skill has real side effects (deploying to production). Confirm each step with the user before executing.
Before deploying, verify:
npm run build
next.config.ts for frame-ancestors:// next.config.ts must include:
headers: [
{
source: "/(.*)",
headers: [
{
key: "Content-Security-Policy",
value: "frame-ancestors 'self' https://*.sitecorecloud.io",
},
],
},
]
Environment variables are set — Check that .env.local exists and has required values
Extension points are registered — All routes defined in the app should be registered in the Developer Portal
npm i -g vercel
vercel link
# For client-side apps
vercel env add NEXT_PUBLIC_SITECORE_APP_ID
# For full-stack (Auth0) apps — add all Auth0 vars too
vercel env add AUTH0_SECRET
vercel env add AUTH0_BASE_URL
vercel env add AUTH0_ISSUER_BASE_URL
vercel env add AUTH0_CLIENT_ID
vercel env add AUTH0_CLIENT_SECRET
vercel env add AUTH0_AUDIENCE
vercel env add AUTH0_SCOPE
# Preview deployment
vercel
# Production deployment
vercel --prod
After deploying:
AUTH0_BASE_URL env var in Vercel to match the production URL (if using Auth0)