Heavy data tables with bulk operations — the back-office workhorse.
The screen that runs the operation. Header strip with system-status pills, dense toolbar with bulk actions (export / archive / reassign / status change), and a high-density DataGrid taking up the full page. For the user who lives in this screen all day and cares about throughput, not aesthetics.
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.
System-state row at the top: error count, warning count, queue depth.
Export, archive, reassign, status change — wide toolbar.
Full-page dense grid with row checkboxes, pinned filters, infinite scroll.
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 Admin Overview 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.