Components

All components

The 75 components a model can use, in 9 packs: what each is for, its attributes, and a live preview drawn by the core.

View as Markdown

Every answer can use the core pack. The others are added by default; an app that names the packs it wants (packs in the API and the SDKs) gets core and those, and the model is told about only those. Fewer packs make a shorter system prompt: core alone is about 1,400 tokens, every pack about 2,900.

Pack Components What it's for
Core 25 Always included: layout, text blocks, numbers, charts, forms and buttons.
Data 7 Ways to show data beyond charts and tables: facts, timelines, gauges, heatmaps, funnels, sparklines and hierarchies.
Commerce 6 Shopping: products, pricing plans, carts, ratings, comparisons and prices.
Device 10 The device's own hardware and apps: maps, camera, scanning, location, files, contacts, the calendar, sharing, voice notes and QR codes. Native on every platform, with a web fallback that needs no JavaScript.
Docs 5 Technical writing: code with a file name, diffs, formulas, file trees and cited sources.
Inputs 6 More form fields: star ratings, searchable choices, times, toggle groups, steppers and signatures.
Interactive 7 Things the reader does on the page, kept on their device and reported back: a quiz, flashcards, a poll, a checklist, and what-if sliders.
Media 4 Video, audio, embeds from known hosts, and a carousel of images.
Scheduling 5 Time: a month calendar, events, time slots to pick, a day's agenda and countdowns.

Names models use on their own

A few names models reach for without being told are read as the component they mean, and reported as a note, never taught:

They write It's read as
<Table> <Card>: a section holding a Markdown table
<Column> a plain group: one cell of Columns
<Buttons> a plain group: a row of buttons
<Text> a plain group: what models call a run of text

Every component