System templates
The polished layouts you start from, before any brand is applied.
System templates are the ready-made layouts that ship with braaand. They're finished, polished designs with no brand baked in, so any brand can pick one up and make it its own.
Two kinds
- Branded. The everyday layouts: hero statements, product cards, sale posters. They take on a brand's colors and fonts on their own.
- Concept. Playful fake-screen designs: a notes app, an iMessage thread, a dating-profile card, a leaked PDF, a sticky note. These look like the thing they're imitating, so they don't follow the brand's fonts and colors the usual way. A brand can still opt in for its logo or accent color where it fits the joke.
How one becomes yours
When an agent picks a system template for your brand, braaand makes a copy and applies your brand to it: your colors and fonts flow in, the right logo gets chosen, and the layout is sized for every format. The result is your own template, fully editable. The original is untouched, so the same system template can be used by a thousand different brands.
You can browse them in the app, and an agent reaches for them by matching your request against what each one is built for (see Why templates).
Layout intent travels with it
A system template is more than positioned boxes. It can also carry the rules that explain how those boxes should behave when an agent rewrites the copy or swaps an image:
- Guides are rails on the canvas: safe margins, bottom lines, center lines, or points of interest for image subjects.
- Clusters are flexible stacks. A heading, subheading, and button can stay centered together, or a checklist can keep even spacing as rows wrap.
- Groups are frozen sub-arrangements. Use them for row/card units whose insides should stay exactly arranged, like a checkbox plus its label.
- BrandFit rules decide which deterministic layout fixes run automatically or on demand.
Those fields are copied from the system template into the brand template, and then into every creative made from it. A complex template can therefore arrive with its own behavior intact: an agent changes words, calls BrandFit, and the layout settles without hand-moving everything.
Reusable rows and cards
Groups and clusters work especially well together. Put each row or card into a group, then make those groups members of one parent cluster. Mark the best source group as reusable. An agent can then clone that group, swap the new text or image, append it to the cluster, and BrandFit stacks the whole list cleanly.
This is the pattern to use for checklist concepts, ranked lists, repeated cards, chat-message rows, quote lists, and any template where "add one more item" should be a normal agent action rather than a redesign.
Agent routes
Agents can see the system-template catalog and copy a layout into a brand:
braaand system-templates list
braaand system-templates instantiate hero-statement --brand <brandId>Once instantiated, the copy is a normal brand template. Edit it with the template editor, templates update, or MCP tools like update_template_element. For a client layout that should not become part of the global catalog, start a brand template directly with templates create or create_template.