TEMPLATES

WHAT ARE TEMPLATES?

A template is a saved snapshot of a pipeline's Stage 1 configuration. It captures:

• • Prompt text — the initial instruction or request you've written in Stage 1
• • Chip selections — all five chip categories (AI Mind, Prerequisites, Implementation, Tools, No-Go) with the specific chips you've activated
• • Pipeline name and description — metadata that identifies the template's purpose
• • Focus tags — any tags associated with the pipeline

When you use a template, Synthezer creates a brand-new pipeline pre-filled with all of these settings. You can then modify anything before submitting Stage 1 — templates are a starting point, not a locked configuration.

WHY USE TEMPLATES?

BUILT-IN TEMPLATES

Synthezer ships with four built-in templates that cover common workflows. These are always available and cannot be deleted.

LOADING A TEMPLATE

There are two ways to start a new pipeline from a template:

OPTION 1: FROM THE DASHBOARD

1. 1. On the dashboard, click From Template in the quick actions panel.
2. 2. The template selector modal opens, showing all built-in templates and any user-created templates.
3. 3. Click Use Template on the one you want.
4. 4. A new pipeline is created with Stage 1 pre-filled. You can edit the prompt, add or remove chips, then submit.

OPTION 2: FROM THE COMMAND BAR

1. 1. Open the command bar with Ctrl+K (or Cmd+K on Mac).
2. 2. Type "template" to filter actions.
3. 3. Select the template action to open the template selector.

CREATING A TEMPLATE

You can save any pipeline's Stage 1 configuration as a reusable template.

1. 1. Set up Stage 1 — write your prompt and select the chips you want included in the template.
2. 2. Click the Save Template button in the top toolbar of the active pipeline view (the bookmark icon).
3. 3. In the modal that appears, enter a template name (e.g., "Code Review Pipeline") and an optional description.
4. 4. Click Save Template to confirm.

MANAGING TEMPLATES

WHERE TEMPLATES ARE STORED

User-created templates are stored in your browser's local storage under the key synthezer_templates. They persist between sessions as long as you don't clear your browser data. Built-in templates are hardcoded in the application and are always available.

VIEWING YOUR TEMPLATES

Open the template selector (dashboard → From Template) to see all available templates. User-created templates appear alongside the built-in ones and are labeled User Template.

TEMPLATE COUNT

You can see how many templates you have saved in the AI → Profile tab under the Browser Storage section, where the template count is displayed.

DELETING TEMPLATES

To remove all user-created templates, go to AI → Profile → Danger Zone and click Clear All Browser Data. This removes templates along with all other browser-stored settings.

TEMPLATES VS CHIP PACKS

Synthezer has two features that let you reuse configurations. Here's how they differ:

Use templates when you want a complete starting point (prompt + chips). Use chip packs when you just want to quickly load a set of chips into any pipeline.

SHARING TEMPLATES

Synthezer provides two ways to share templates with others.

EXPORT INDIVIDUAL TEMPLATES

1. 1. Open the template selector (dashboard → From Template).
2. 2. User-created templates show an Export button.
3. 3. Click Export to download the template as a .json file.
4. 4. Share the JSON file with anyone. They can import it via the Profile system.

EXPORT VIA PROFILE

Templates are also included automatically in a full profile export. Go to AI → Profile → Export Data to download your entire Synthezer profile, which bundles templates together with your pipelines, chips, chip packs, and other settings.

When someone imports your profile, your templates are restored into their browser alongside everything else. See the Profile tab documentation for full details on export and import.

TEMPLATE FILE FORMAT

Exported templates are JSON files with this structure:

{
  "id": "user_1707500000000",
  "source": "user",
  "name": "My Code Review",
  "description": "Structured review with actionable feedback.",
  "focusTags": ["code", "analysis"],
  "stage1": {
    "prompt": "Review the provided codebase...",
    "chips": {
      "ai_mind": ["PRECISION", "THOROUGH"],
      "prerequisite": ["UNDERSTAND CODEBASE", "READ DOCS"],
      "implementation": ["CODE", "API"],
      "tools": ["TERMINAL"],
      "no_go": ["NO BREAKING CHANGES"]
    }
  }
}

Each field explained:

• • id — unique identifier (auto-generated from timestamp for user templates)
• • source — "user" for custom templates (built-in templates omit this field)
• • name — display name shown in the template selector
• • description — short description of the template's purpose
• • focusTags — array of tags for categorization
• • stage1.prompt — the prompt text pre-filled in Stage 1
• • stage1.chips — object with five arrays, one per chip category

BEST PRACTICES