A template tells the agent three things: the output format to build, the viewer to open the result in, and the design-kit rules to check it by. Pick one at project creation — or leave Blank and let the brief decide. Each page in this section covers one template in depth.
The 14
| Template | Builds | Viewer |
|---|---|---|
| UI mockups & wireframes | App screens and lo-fi flows | Live preview + artboard grid |
| Slides | Full presentation decks | Slide viewer + thumbnails |
| Mobile app | Phone-sized screen sets | Multi-artboard board |
| Interactive website | Working multi-page sites | Live preview |
| Brand & logo | Logo marks + brand kits | Brand board |
| 3D object | Models and scenes | Orbit viewport + scene editor |
| Animation | Motion pieces | Animation player |
| Résumé | One-page CVs | Document preview |
| Infographic | Data stories | Document preview |
| HTML email | Client-safe emails | Client-width preview |
| Document & research | Reports and long-form | Document preview |
| Blank | Whatever the brief says | Live preview |
…plus specialized project kinds that share the same engine.
What a template changes
- The build — structure, file layout and libraries the agent reaches for
- The viewer — how the result presents (a deck gets slides, 3D gets orbit)
- The checks — which gate rules apply (a slide's type floor isn't a mobile screen's hit-target rule)
- The exports — which output formats the result can render (see Per-template exports)
Which to pick
Reach for the template that matches the output, not the subject — a pitch deck about a mobile app is still Slides. When the deliverable is a website, it's Interactive website; when it's a picture of a screen, it's UI mockups or Mobile app.
Tip: Blank is for when you genuinely don't know the shape yet — every other case picks a template, because the viewer and checks it loads are how the agent knows what "done" looks like.