Design Templates
Prerequisites
- Read
navigation or call view-screen when the current template or design
is unclear.
- Treat built-in and user-created entries as one template concept. Their
ownership and available share/delete actions differ, but creation uses the
same action.
Workflow
- Resolve the starting point. When the user mentions a template, past
design, or prior work, call both
list-design-templates and list-designs
before generating. Match the requested name or id; ask only when multiple
plausible results remain. To look through a template before using it, call
get-design-template --templateId="<id>" (read-only); in the UI a template
card opens the same read-only preview, and its "Use template" button is the
copy step. Built-in starters include app screens (analytics dashboard,
messaging app, project tasks, design studio) beside ads, posters and pages.
- Save a reusable template. Call
save-design-as-template with the source
designId. The action snapshots inline screens, canvas dimensions,
defaults, linked design system, and locked layers.
- Create from a template. Call
create-design-from-template with the
resolved templateId. Pass designSystemId only when the user selected an
override; the action access-checks it and returns the effective linked id.
- Stop after a pure copy. If there is no prompt and no pending design-system
adaptation, open the copied design and do not start generation.
- Adapt copied screens. When the user supplied a prompt or chose a
different accessible design system, call
get-design-snapshot exactly once,
then refine the existing unlocked content with edit-design. Never call
generate-design, delete the copied screens, or recreate the template from
scratch.
- Verify. Read back the copied design and confirm its screens, canvas
dimensions, linked design system, and locked-layer boundaries before
reporting completion.
The Template On Follow-Up Requests
A copied screen is edited in place. After the first refinement saves, the
design's own files are the result, not the template — so a later turn that
reads only get-design-snapshot has no idea what the template specified, and
fonts and artboard dimensions drift a little further on each request.
The two facts that drift are cheap, so they arrive on their own. view-screen
reports design.createdFromTemplate on every turn for a template-created
design, carrying lockedDimensions per screen and lockedFonts. Both are
captured from the template at copy time, so they describe the template even
after the design has been edited many times. Honour them in every
edit-design pass: never resize the artboard, change a canvasFrames width or
height, switch the primary viewport, or substitute a typeface to fit new
content.
Call get-design-template --designId="<id>" when you need more than those two
facts — the template's original markup, or its locked layers — for example
before a structural edit or when the user asks how far the design has moved
from its template. The full template files are large, which is why they are a
deliberate second call rather than part of every turn.
Locked Layers
data-agent-native-locked="true" is authoritative. Keep each locked element
and all descendants byte-for-byte unchanged during adaptation. If the user
explicitly wants one changed, ask them to unlock it in the Layers panel first.
Ownership
- Built-in templates cannot be renamed, shared, or deleted.
- Owned user templates may be shared with the standard resource sharing UI and
deleted with
delete-design-template.
- Do not model templates as ordinary
designs rows and do not invent alternate
template action names.
Related Skills
design-generation — creating and refining Design screens.
design-systems — applying linked systems and tokens.
sharing — access and sharing rules for user-created templates.
1---2name: design-templates3description: >-4 Find, save, copy, and adapt Design templates. Use when the user references a5 template, a prior design, or wants a reusable starting point.6metadata:7 source: https://skillmd.com/skills/builderio/design-templates8---910# Design Templates1112## Prerequisites1314- Read `navigation` or call `view-screen` when the current template or design15 is unclear.16- Treat built-in and user-created entries as one template concept. Their17 ownership and available share/delete actions differ, but creation uses the18 same action.1920## Workflow21221. **Resolve the starting point.** When the user mentions a template, past23 design, or prior work, call both `list-design-templates` and `list-designs`24 before generating. Match the requested name or id; ask only when multiple25 plausible results remain. To look through a template before using it, call26 `get-design-template --templateId="<id>"` (read-only); in the UI a template27 card opens the same read-only preview, and its "Use template" button is the28 copy step. Built-in starters include app screens (analytics dashboard,29 messaging app, project tasks, design studio) beside ads, posters and pages.302. **Save a reusable template.** Call `save-design-as-template` with the source31 `designId`. The action snapshots inline screens, canvas dimensions,32 defaults, linked design system, and locked layers.333. **Create from a template.** Call `create-design-from-template` with the34 resolved `templateId`. Pass `designSystemId` only when the user selected an35 override; the action access-checks it and returns the effective linked id.364. **Stop after a pure copy.** If there is no prompt and no pending design-system37 adaptation, open the copied design and do not start generation.385. **Adapt copied screens.** When the user supplied a prompt or chose a39 different accessible design system, call `get-design-snapshot` exactly once,40 then refine the existing unlocked content with `edit-design`. Never call41 `generate-design`, delete the copied screens, or recreate the template from42 scratch.436. **Verify.** Read back the copied design and confirm its screens, canvas44 dimensions, linked design system, and locked-layer boundaries before45 reporting completion.4647## The Template On Follow-Up Requests4849A copied screen is edited in place. After the first refinement saves, the50design's own files are the *result*, not the template — so a later turn that51reads only `get-design-snapshot` has no idea what the template specified, and52fonts and artboard dimensions drift a little further on each request.5354The two facts that drift are cheap, so they arrive on their own. `view-screen`55reports `design.createdFromTemplate` on every turn for a template-created56design, carrying `lockedDimensions` per screen and `lockedFonts`. Both are57captured from the template at copy time, so they describe the template even58after the design has been edited many times. Honour them in every59`edit-design` pass: never resize the artboard, change a `canvasFrames` width or60height, switch the primary viewport, or substitute a typeface to fit new61content.6263Call `get-design-template --designId="<id>"` when you need more than those two64facts — the template's original markup, or its locked layers — for example65before a structural edit or when the user asks how far the design has moved66from its template. The full template files are large, which is why they are a67deliberate second call rather than part of every turn.6869## Locked Layers7071`data-agent-native-locked="true"` is authoritative. Keep each locked element72and all descendants byte-for-byte unchanged during adaptation. If the user73explicitly wants one changed, ask them to unlock it in the Layers panel first.7475## Ownership7677- Built-in templates cannot be renamed, shared, or deleted.78- Owned user templates may be shared with the standard resource sharing UI and79 deleted with `delete-design-template`.80- Do not model templates as ordinary `designs` rows and do not invent alternate81 template action names.8283## Related Skills8485- `design-generation` — creating and refining Design screens.86- `design-systems` — applying linked systems and tokens.87- `sharing` — access and sharing rules for user-created templates.