Templates
Templates are pre-built starting points for common app types. Instead of building from scratch, you start with a working skeleton and customize from there.
Why use a template?
- Faster start — The AI has less work to do upfront, so your first preview is ready sooner.
- Better structure — Templates follow proven patterns for their app type, so you get a solid foundation.
- Less back-and-forth — Common features (search, filters, forms, tables) are already wired up.
That said, templates are just starting points — not limitations. You can ask the AI to add, remove, or completely change anything after picking one.
How to pick one
When creating a new project, you'll see a template picker. Browse by category or search by name. Pick the one that most closely matches what you're building — even a loose match is better than starting from scratch.
If nothing fits, skip the template entirely and describe your app from scratch.
KV vs SQL variants
Many templates come in two flavors:
| Variant | Name example | Best for |
|---|---|---|
| KV (default) | crm | Most apps — fast, flexible, no setup |
| SQL | crm-sql | Apps needing complex queries or reports |
When in doubt, pick the plain version (no -sql). You can always switch later.
→ Learn more about storage options