Skip to main content

Work with templates

Templates let Builder teams standardize faster starts instead of rebuilding the same foundations repeatedly.

Template views​

The Templates area has two main views:

  • Community for official and community starters
  • Mine for templates you manage in your own workspace

Discover community templates​

In the community view, you can browse by:

  • Popular
  • New
  • Official
  • Community

Template cards show key signals such as:

  • official vs community source
  • preview image
  • template description
  • total installs

Open a template detail page​

The detail page is where teams decide whether a template is worth adopting.

It includes:

  • full template branding and description
  • install count
  • update date
  • quick preview for the live starter
  • the Use template action

Use a template​

When you select Use template, Builder creates a fresh app from that starter and opens a new chat on the resulting project.

This is the fastest path when:

  • you want a proven baseline
  • you need a consistent internal starter
  • the visual or data structure already exists in a template form

Save your own app as a template​

In hosted Builder, save reusable apps from App Details using Save as Template.

This is useful when you have:

  • a reliable internal starter
  • a repeatable product pattern
  • a polished project worth sharing more broadly

When saving, you define the template's:

  • name
  • description
  • visibility
  • preview image

Public vs private templates​

  • Private templates stay inside your managed workspace context.
  • Public templates can be exposed as reusable marketplace starters.

Use private templates for internal systems, brand-specific starters, or opinionated team workflows.

Manage your own templates​

From Mine, you can:

  • edit template details
  • change visibility
  • open the public page for shared templates
  • delete old templates

When templates are better than prompts​

Use a template when you want to preserve:

  • structure
  • files
  • setup decisions
  • starter flows

Use a prompt when you only want to preserve instructions.

Continue: Store prompts and theme prompts in Library