Earlier formats
Section templates
Ready-made navbars, heroes, pricing sections, and app screens, built only from the component set. An agent fetches one over MCP and changes the words.
A mockup of a website or an app is mostly sections people have seen before: a navbar, a hero, three pricing plans, a sign-in screen. A section template is one of those, already drawn with the component set, so an agent starts from a section that works and spends its effort on your words.
What a template isLink to this section
A template is a piece of a ui spec: a root element, the elements under it, and the state they read. It uses only components from the set, so it follows the artifact's theme, light and dark, and lays itself out by the width it is drawn at: the page, or a canvas frame. Every template keeps the same rules.
| Rule | What it means |
|---|---|
| Size | At most 60 elements, nested at most 10 deep, so six or more fit in one spec. |
| Lists | A list (plans, links, features) lives in the template's state and is drawn by one repeat. Change the list, not the elements. |
| Words | Placeholder copy, written for this set. No company names and no real logos. The one exception is a brand mark (`brand-` icons) on a social profile button, or on a Continue with Google, Apple, or GitHub button. |
| Media | Placeholder stands in for images, logos, video, and maps. A template needs no upload. |
| Links | Links go nowhere, as in any mockup. |
| Style | Only the component set's named steps: no CSS, no colors, no class names. |
Use one over MCPLink to this section
Two read-only tools hand templates out (MCP reference). ui_templates_list returns one small row per template, all of them or only one category or kind. ui_template_get returns one template, ready to use:
{ "id": "pricing-three-tiers", "prefix": "plans", "as": "fragment" }{ "id": "pricing-three-tiers", "prefix": "plans",
"slots": [ { "what": "Headline", "element": "plans-title", "prop": "text" },
{ "what": "Plans, each with name, monthly and yearly price, …", "state": "/plans/plans" } ],
"attach": "Add fragment.elements to your spec's elements, add fragment.state's one key …",
"fragment": { "root": "plans-pricing",
"elements": { "plans-pricing": { "type": "Box", … }, "plans-title": { "type": "Heading", … }, … },
"state": { "plans": { "yearly": false, "plans": [ … ] } } } }slotsnames what to change: a prop of one element, or a value in the state, such as the list a repeat draws.as: "fragment"(the default) is a piece to add to a spec the agent is building.as: "spec"is a complete ui spec: save it as a ui artifact, or use it as a canvas frame'sspec.attachsays, in one sentence, how to use what came back.
Several in one pageLink to this section
Every element key and state path of a template carries a prefix: the template's id, or the prefix the agent passes. Keys become plans-title, and the state moves under /plans. So a navbar, a hero, and a pricing section share one spec without a clash, and one template can be used twice under two prefixes. The spec form wraps the template in a root Box named page; further sections go into its children.
The templatesLink to this section
60 templates today. Each name opens the template, drawn by the same renderer an artifact uses, on the page of its category. The category is also what ui_templates_list filters by.
| Template | Id | Category | Made for | Elements |
|---|---|---|---|---|
| Navbar, links right | navbar-basic | navbar | any width | 15 |
| Navbar with open mobile menu | navbar-collapsible | navbar | any width | 16 |
| Navbar, centered logo | navbar-centered-logo | navbar | any width | 17 |
| Navbar with mega menu | navbar-mega-menu | navbar | any width | 46 |
| Announcement banner | banner-announcement | banner | any width | 7 |
| Footer, link columns | footer-columns | footer | any width | 31 |
| Footer, one row | footer-simple | footer | any width | 5 |
| Footer, centered with social links | footer-centered-social | footer | any width | 9 |
| Hero, centered | hero-centered | hero | any width | 9 |
| Hero, media right | hero-split-right | hero | any width | 14 |
| Hero, media left | hero-split-left | hero | any width | 10 |
| Hero with product shot | hero-product-shot | hero | any width | 10 |
| Hero with email field | hero-email-capture | hero | any width | 12 |
| Hero with sign-up card | hero-signup-card | hero | any width | 17 |
| Call to action, centered band | cta-centered-band | cta | any width | 7 |
| Call to action, split card | cta-split-card | cta | any width | 8 |
| Call to action with email field | cta-email-capture | cta | any width | 10 |
| Feature grid, three columns | feature-grid-3 | feature | any width | 11 |
| Feature cards, heading left | feature-grid-2x2 | feature | any width | 12 |
| Feature rows, alternating | feature-zigzag | feature | any width | 14 |
| Feature checklist beside a picture | feature-list-with-image | feature | any width | 11 |
| Feature tabs | feature-tabs | feature | any width | 27 |
| Feature list, heading left | feature-heading-left-list | feature | any width | 11 |
| Feature tiles, mixed sizes | feature-bento | feature | any width | 25 |
| How it works, three steps | process-steps | process | any width | 12 |
| Numbers, four in a row | stats-row | stats | any width | 6 |
| Numbers beside text | stats-split-text | stats | any width | 12 |
| Logo row | logos-row | logos | any width | 4 |
| Pricing, three tiers | pricing-three-tiers | pricing | any width | 17 |
| Pricing, two tiers and enterprise | pricing-two-tiers-enterprise | pricing | any width | 22 |
| Pricing, one plan | pricing-single-plan | pricing | any width | 14 |
| Pricing, plans in rows | pricing-plan-rows | pricing | any width | 18 |
| Comparison, plans by feature | comparison-matrix | comparison | any width | 10 |
| Questions, centered | faq-accordion-centered | faq | any width | 11 |
| Questions, heading left | faq-two-column | faq | any width | 15 |
| Questions with a contact card | faq-contact-card | faq | any width | 18 |
| Testimonial, one big quote | testimonial-single-quote | testimonial | any width | 10 |
| Testimonials, three cards | testimonial-grid-3 | testimonial | any width | 15 |
| Testimonials, one featured and two more | testimonial-featured-plus-cards | testimonial | any width | 20 |
| Team, four across | team-grid-4 | team | any width | 14 |
| Team, list with bios | team-list-bio | team | any width | 13 |
| Blog, three cards | blog-grid-3 | blog | any width | 15 |
| Blog, featured post and list | blog-featured-list | blog | any width | 16 |
| Contact, form and details | contact-form-info | contact | any width | 28 |
| Contact, cards and a map | contact-cards-map | contact | any width | 15 |
| Newsletter, one line | newsletter-inline | newsletter | any width | 11 |
| Sign in, centered card | auth-sign-in-card | auth | any width | 21 |
| Sign in, split screen | auth-sign-in-split | auth | any width | 28 |
| Sign up, centered card | auth-sign-up-card | auth | any width | 16 |
| App shell, left sidebar | shell-sidebar | shell | any width | 53 |
| Dashboard overview | dashboard-overview | dashboard | any width | 22 |
| Table with filters | table-filters | table | any width | 22 |
| Detail view with side panel | detail-side-panel | detail | any width | 31 |
| Settings form | settings-sections | settings | any width | 28 |
| Empty state | empty-first-item | empty | any width | 12 |
| Error 404 | error-not-found | error | any width | 12 |
| Confirm dialog | modal-confirm-delete | modal | any width | 12 |
| Command menu | command-search | command | any width | 25 |
| Notification list | notifications-by-day | notifications | any width | 27 |
| Checkout with order summary | checkout-summary | checkout | any width | 39 |