Templates

For supply-chain, fleet and field-operations teams

Open exceptions, the network map and the shipment behind every late promise.

For e-commerce operations teams

Orders, stock and prices for a web shop behind one set of tabs in the workspace shell: the orders master / detail grid, a replenishment grid grouped by warehouse with an order-now flag and typed, pasted or filled-down order quantities, and the price list editor.

For process-mining and operations-excellence tools

Process mining on an order-to-cash log: the map, variants and throughput.

For project, issue-tracking and delivery tools

Projects, an issue board, team load and members as one product.

For pricing, trading and treasury products

A market tape, a watchlist and an order ticket with a review step.

For controllers and finance teams

A month-end close workspace for controllers: a journal-entry DataGrid grouped by account with totals, in-place status and memo edits guarded by validation, saved views, Excel export and a Post approved bulk action with Undo, plus the cost-centre re-forecast tree and a summoned close assistant.

For revenue, finance and BI teams

Revenue against plan, the pipeline behind it and an analyst on call.

For account, success and CRM products

One account before the call: health, usage, people and next actions.

For support, service and helpdesk products

A ticket queue, the conversation and a reply drafted from past tickets.

For copilots and agentic products

An agent workspace with reasoning, tools, approvals and sources.

For teams running AI agents in production

A control room for agents in production: spend, traces, reviews and the audit log.

For agent builders, automation platforms and internal AI teams

Design an agent, equip it with skills and MCP servers, then watch its runs.

For products where the agent answers with a screen, not a paragraph

An assistant that answers with screens, streamed in as A2UI data.

A coding-agent session, drawn with the terminal package.

For platform teams, release managers and the engineers whose run just went red

A delivery team's control room: the headline computed from today's runs (how many failed, whether main is green, when production last changed), the four DORA figures as MetricCards computed from 28 days of deploy history, the pipeline as a CanvasShell graph whose nodes take the selected run's stage results beside the run log in a Terminal — selecting a stage narrows the log to it — today's runs as a DataTable under a FilterBar over status and service, the audit-log block as the platform's trail, and a dock the selection summons: the run in Descriptions, the failing check and the change under test as a DiffEditor. Re-run failed stage re-queues the run, steps the sidebar badge down and appends an audit entry, with an Undo in the toast.

For reliability, observability and platform teams

One live incident: error rate, blast radius and a runbook that runs.

For utilities, industrial energy managers and grid operators

Eight sites on the grid: who buys above contract, the alarms and an analyst over the meters.

For security operations teams, incident responders and detection engineers

The alert queue, the assets it fires from and an analyst waiting for the go to contain.

For a company about page

A company about page.

For a signed-in account page of a store or community

A signed-in account page of a store or community.

For a blog index page

A blog index page.

For a single blog post

A single blog post.

For a careers page with open roles

A careers page with open roles.

For a customers / case-studies index page

A customers / case-studies index page.

For a product changelog page

A product changelog page.

For the checkout route of a store

The checkout route of a store.

For a pre-launch / waitlist page

A pre-launch / waitlist page.

For a versus / alternative-to page

A versus / alternative-to page.

For a contact page

A contact page.

For a single customer story

A single customer story.

For a developer-facing landing page: install, code, integrate

A developer-facing landing page: install, code, integrate.

For a long-form features page

A long-form features page.

For the password-reset route

The password-reset route.

For a help center / support landing page

A help center / support landing page.

For an integrations directory page

An integrations directory page.

For the front door of a SaaS product

The front door of a SaaS product.

For the 404 route of a website

The 404 route of a website.

For a pricing page with plans, a comparison table and an FAQ

A pricing page with plans, a comparison table and an FAQ.

For a product detail page of a store

A product detail page of a store.

For a product-led landing page with the product in the hero

A product-led landing page with the product in the hero.

For a resources library page

A resources library page.

For a storefront listing page

A storefront listing page.

For the sign-in route of a product website

The sign-in route of a product website.

For the sign-up route of a product website

The sign-up route of a product website.

For a talk-to-sales page with a bookable walkthrough

A talk-to-sales page with a bookable walkthrough.

A chat that renders tool calls, reasoning and sources, not only text.

A table for browsing and operating on records: search, facets, bulk actions.

The baseline admin console to start a professional app from.

A node canvas with an inspector, for pipelines and agent graphs.

A landing page: hero, feature grid, stats and a call to action.

Master-detail: a searchable list driving a tabbed record view.

One representative data screen (Customers) rendered across the FULL state grid — Ready, Loading, Empty, Error, FirstRun — with the same chrome and the real state primitives (Table, Skeleton, StatePanel kind="empty"|"error").

Grouped forms with sections, descriptions and saved state.