Make a template

Turn a page you made into a pattern you can use again.

guide~2 minVerified v0.71.0

The artifact Settings card with Copy template prompt and the proposed template slug. — Settings hands your agent the artifact-specific prompt.

You will have a reusable pattern and a fresh artifact built from it.

Turn your KPI board into a template

Promote my artifact "Weekly KPI board" into a reusable Super Artifacts template.

Read super_template_save's schema before you start. The short version: a template is the
PATTERN this artifact is an instance of, not the artifact. Do not send this artifact's files
unchanged.

The artifact:
- id: <artifact id>
- slug: weekly-kpi
- kind: dashboard
- live at: <artifact URL>
- files: index.html
- collects: nothing

What to do:
1. Read the artifact's own code with super_artifacts {artifact: "<artifact id>", path} — one call
   per file above. Do not fetch its URL; anything not public redirects to a sign-in page.
2. List the DISTINCT components in it. Forty rows of the same card is one card component,
   not forty. Sixty slides of five layouts is five layouts.
3. Write the runtime as that list, once each, driven by a
   `<script id="sa-template-values" type="application/json">` block — exactly one occurrence.
4. Reduce the content to five to ten samples chosen to DEMONSTRATE VARIETY, not volume. One
   of every component, every field type, the empty state, the finish state.
5. Turn everything that varies between instances into a slot. Name the slots for what they
   are, never for what this artifact's content happened to be.

Then:
- Save it with super_template_save, slug "weekly-kpi-template".
- Include `spec.examplePrompts`: five or six sentences I could paste at an agent to get an
  artifact out of this blueprint.
- Include a `sample` that shows one of every component — it is what the marketplace renders
  and photographs, so it is the blueprint’s shop window rather than test data.
- Build one instance from it with super_publish (`template` and `values`) and show me both URLs.

If the instance is not as good as the artifact you started from, the template is not
finished. Tell me what is missing rather than shipping it.

Keep the pattern

The Template card on Settings (or Template and workspace shelf) copies the product's prompt for that artifact. The agent reads its files, keeps one example of each component and turns changing content into slots. super_template_save saves the draft. For a collecting artifact, its declaration and data series carry into the template too.

A template's Publishing panel showing its second draft version. — A revision advances the draft; release is a separate decision.

A new draft version keeps the previous versions recorded. Feedback from the instance helps you refine the pattern before releasing it. The template's page shows installs, use and ratings as counts, without naming the people using it.

What it costs

One-page KPI board	Median per run
From scratch (n=3)	31,452 tokens processed · 1,534 output tokens · 10.043 seconds
From a template (n=3)	66,428 tokens processed · 1,594 output tokens · 13.479 seconds
Make a template (n=1)	80,939 tokens processed · 5,844 output tokens · 37.08 seconds

These are medians measured on 2026-10-13 with claude-sonnet-5-5 on a private test stack: three runs each from scratch and from a template, and one making a template. The task was a one-page KPI board, with the template already installed. Tokens processed include input, cache reads, cache creation and output, including the agent's system prompt.

The template run used about twice the tokens processed and a bit more time than building from scratch. Output tokens were about equal. A template's value is consistency and reuse, not a measured saving. This small local test does not predict every model or task.

Check it worked

The template page shows the draft version. The new instance opens with different content while keeping the pattern. A saved draft is not yet a marketplace listing.

Next: Release to the marketplace.