Design a complete storefront theme, bind it to a typed data contract, and operate a real store from an AI agent — without ever touching the money path.
$ pnpm theme:create aurora $ MECSTO_DEV_THEME=mecsto/aurora pnpm dev → Demo Studio running at http://localhost:3000
Three ways in, depending on what you are building.
A Next.js package implementing a 14-page contract and 15 composable sections. Build it entirely offline against a fictional demo store, then submit for review.
Front-end engineers34 server loaders and 21 client hooks return typed view-models. You never write a query — you bind to a shape the platform guarantees.
Agent builders55 tools over the Model Context Protocol let an agent read and run a real store, behind an OTP sign-in and explicit consent gates.
Checkout, login and account pages are rendered by the platform on every theme — no theme code runs inside them. Merchant data is read through typed loaders, never raw queries.
That boundary is why a theme can be reviewed as a design and shipped, instead of audited for payment bugs.
How the money path works →// your theme <Link href="/checkout">Book now</Link> // the platform takes it from here: // pricing · tax · promotions · loyalty // payment · webhook · receipt
Every figure is generated from the platform source at build time. Delete a loader and it leaves these docs automatically.