Record header + tabbed main + side rail metadata — the canonical record page.
A generic detail view for any single record: order, account, ticket, project. Header strip up top with the record's identity + status + primary actions, a tabbed main area for the heavy content (overview / activity / files / related), and a right-side metadata rail with the fields that don't need to be in the user's face. The template you reach for whenever a user clicks a row.
Each section pre-wired with the right CleenUI primitives. Swap, remove, or extend any of them — the template is a starting point, not a constraint.
Record name, status pill, primary actions on the right.
Overview / Activity / Files / Related — the deep content lives here.
Right-side fields: owner, created, modified, tags, IDs.
All of these are in the catalog — the Builder skill imports them automatically. Each chip links to that component's page.
When the Builder skill scaffolds this template for you, these are the fields it asks about — or infers from your prompt.
Ask your AI agent to scaffold this template in your project — the Builder skill knows the Detail Screen layout and the components it uses.
Two paths to your first component. Pick the one that fits how your team builds.
One prompt to your AI tool. The Setup skill handles dependencies, design tokens, build config, and component registration — all without leaving your editor.
The classic flow. Install the package, import the styles, drop in your first component. No agents required — same end result.