A finished storefront, not a scaffold.
Every page a shopper needs is already built and wired to your backend — the work left is making it look like your brand.
The shopping path
All of it ships working against the active connector.
Catalogue
Listing pages, category routes, filters, sorting, pagination and search.
Product detail
Gallery, variants, options, stock state, related products and reviews.
Cart
Line items, quantity, removal, subtotals and a coupon drawer.
Checkout
Address, shipping, payment method, order processing and a success page.
Account
Orders and order detail, addresses, profile, wishlist, password reset.
Auth
Email and OTP login, signup, forgot and change password, post-auth redirect.
Platform
SSR and SPA
Server-rendered first paint for crawlers and cold loads, client-side navigation after. Installable as a PWA.
Switchable themes
Themes are selectable implementations resolved at runtime from config or store settings — never forks of the routes.
Typed end to end
TypeScript across routes, services and connectors. npm run check is a single pass or fail signal.
Deploy anywhere
Netlify and Vercel with zero config, a Node adapter for your own server, or the published Docker image.
Built to be edited
The same separation that keeps a team sane is what lets an agent work safely.
- Commerce is reachable only through
$lib/core/services— no component names a backend. - The backend is one export in
kitcommerce.config.ts. - Theme copy, imagery and section content live in the theme layer, not inline in routes.
- Svelte 5 runes, Tailwind and shadcn — conventions with deep training coverage.
Start with your backend.
Clone it, point it at your API, and describe the store you want.