Prismic Slice Machine
Local CLI that turns coded slices into a Prismic page builder
Slice Machine is Prismic's local development tool for content modelling. You build reusable page sections (slices) as real components in your codebase, and Slice Machine publishes their content models to Prismic so marketers can assemble pages in a visual page builder. It has first-party adapters for Next.js, Nuxt and SvelteKit, runs a local slice simulator, and generates typed definitions for @prismicio/client. Prismic's own docs now steer new projects toward the cloud Type Builder instead, so check which one a project already uses.
npx @slicemachine/initUse this when a Next, Nuxt or SvelteKit marketing site needs pages that non-developers can rearrange, and the team has already chosen Prismic — it is not a general CMS choice, it is the modelling layer for one. Run `npx @slicemachine/init` inside the existing app rather than scaffolding from it, then re-run type generation after every model change or `@prismicio/client` will hand you stale types. Before you add models, confirm whether the project is on Slice Machine or on Prismic's newer cloud Type Builder; mixing the two is the usual source of drift.
Why it is here. It is the clearest example of the code-first page-builder pattern: developers own the component, marketers own the composition, and neither edits the other's layer.
- slices are real code components
- local slice simulator
- Next, Nuxt and SvelteKit adapters
- generates TypeScript types
- being superseded by the cloud Type Builder
Verified 2026-08-15. HTTP 200. https://prismic.io/slice-machine, https://prismic.io/docs/slice-machine
