Templates
{{templates}} complete flagship apps — real screens, data models, handlers, and tests — that you start from and shape with AI.
What templates are
Templates are complete, polished apps — 152 of them: blog, CRM, team chat, online store, kanban, hotel booking, helpdesk, AI chatbot builder, database admin, and more. They are the recommended starting point because they replace the blank page with working software you shape.
Each one is real files, not a generator’s promise: screens with polished UX, a data model with migrations, working API handlers, fixtures for realistic previews, and its own e2e specs. Every template’s page (browse them) shows the screens, the data model, the packages it is built from, and a live preview you can open and run.
Starting from one
npx mlcl templates # browse the gallery
npx mlcl create store --template online-store --no-interactiveIn the IDE, pick the template when you create a project — the preview boots with its fixtures so you see the real app immediately, then describe the changes you want.
Shaping it into yours
A template is a starting point, not a cage. Typical moves, all plain-language requests to the AI (in the IDE or your own agent): rename the brand and recolor, add or remove data-model entities, swap the payments or database provider with `mlcl swap`, add a package capability with `mlcl add --inject`.
Because every template type-checks and passes its own tests out of the box, a change that breaks the contract is visible immediately — the template is the reference implementation your edits are measured against.