Skip to main content

Store prompts and theme prompts in Library

The Library helps Builder teams stop rewriting the same instructions every session.

It includes two reusable asset types:

  • Prompts
  • Theme Prompts

Use prompts for reusable build instructions​

Prompts are workspace-level instructions you want Builder to reuse across apps or chats.

Good prompt candidates include:

  • product scaffolding rules
  • QA or release checklists
  • house style instructions
  • repeated workflow commands

If a prompt has a slug, it can also work as a slash command.

Use theme prompts for visual direction​

Theme prompts capture the design system or art direction you want Builder to follow.

Use them when you want repeatable control over:

  • typography style
  • layout tone
  • color and surface direction
  • interaction feel
  • brand-specific visual guidance

Create theme prompts manually or with AI​

Builder supports two paths for theme prompt creation:

  • AI-Powered: generate a theme prompt from references such as screenshots or a live website
  • Manual: write the reusable design instruction yourself

This is especially useful when a team wants Builder output to feel consistent across multiple projects.

When to use prompts vs theme prompts​

Use Prompts for product or workflow instructions.

Use Theme Prompts for visual direction.

Many teams keep both:

  • a prompt for how the app should behave
  • a theme prompt for how the app should look

Good Library hygiene​

Keep Library assets easy to trust:

  • give each entry a specific name
  • describe when it should be used
  • delete stale or duplicate assets
  • keep each prompt focused on one job

Good prompt examples​

  • "Internal admin dashboard starter"
  • "Customer-facing onboarding flow copy style"
  • "Enterprise settings page QA checklist"
  • "Bold editorial landing page theme"

When Library matters most​

Library becomes especially valuable when:

  • multiple teammates use Builder in the same workspace
  • you are building families of related apps
  • your team wants a recognizable house style
  • you keep repeating the same setup or design guidance