Blocks
A component is a part of a screen. A block is the whole section, with the Pro components already wired to each other. Landing page sections, and app screens like auth, settings and dashboards. Each one installs as a single file alongside the components it uses.
Agent Console
1An AI agent at work in one panel. The run on the left, its output on the right, and the budget it spent along the bottom.
Agent Thread
2An AI chat that streams word by word, shows its tool calls, asks before it acts, and cites its sources. As a full page or a docked copilot.
Agent Workspace
1One place for an agent run. A prompt with a border beam while it works, the plan ticking off, then an answer with its sources.
Auth
4Sign in, sign up, a one time code and a password reset, all sharing one form kit with inline errors and loading buttons that never resize.
Contact
1A contact section. The ways to reach you beside a form that checks itself and turns into a thank you.
CTA
2The closing ask of a landing page. A centered panel with two actions, or the pitch beside the product itself.
Dashboard
1An analytics dashboard in one section. A date range switch, a row of numbers, a bar run, a donut, a ranked list and a year of activity.
Empty State
3What a screen shows before there is anything on it. What goes here, and the fastest way to put the first thing in.
Error Page
2The pages for when something goes wrong. A 404 that helps people find their way, and a friendly error with a retry.
FAQ Wall
1The questions that always follow a price, as disclosures that open without a layout pass, with a way out at the bottom.
Feature Grid
1A bento features section. A wide before and after, a card that turns over, and tiles that slide their detail out on hover.
Hero
2The top of a landing page, as a launch announcement or as a centered pitch over the product itself.
Invoice
2Invoices for a SaaS app. A document that prints clean, and a list you filter by status and open in place.
Pricing Wall
1A billing switch, a row of plan cards where the featured one costs no extra height, and the questions that always follow a price.
Proof Wall
1A row of numbers, a wall of quote cards that reflows to one column on a phone, and a logo row underneath. The section every landing page needs once it has customers.
Settings
3The account screens every app needs. A profile that saves only when changed, billing with usage and invoices, and a team you can invite to.