Templates are pre-written prompts for app types that come up often. Pick one and the app builder runs the same build flow it would for a custom prompt — interview, plan, build — but with a head start.
Templates aren’t finished apps. They’re starting points. You’ll still get a chance to shape the plan, and you’ll still iterate after the build.
Browsing templates
Click Add App in the sidebar and stay on the Build tab. The row below the prompt box shows the first set of templates organized by category. Click More to see the full catalog.
The categories cover the patterns we see firms reach for most often:
Customizing a template
When you pick a template, the prompt populates with the template’s text. Edit it before clicking Build — change the language to match your firm, add specifics, remove anything that doesn’t apply.
The product agent will still run its interview. Template or not, the app builder asks the questions it needs to fit the app to your workflow.
When to start blank
Templates are useful when you recognize the pattern. They’re a distraction when you have something specific in mind that doesn’t match any of them.
Start blank when:
- You have a clear picture of the app and want to describe it directly
- Your need is firm-specific and doesn’t fit a generic pattern
- You’re more comfortable writing from scratch than editing a starting point
Start from a template when:
- You’re not sure how to phrase what you want
- You recognize one of the categories above as close to your need
- You want to see how the app builder frames a common pattern before customizing
Browse the templates even if you plan to start blank. They’re useful as a reference for how to phrase prompts and what level of detail the app builder expects.
