agent dashboard shell

sources

implementation steps

1. Start with HeaderShell or SidebarHeaderShell so navigation, page title, and primary actions share one stable chassis.
2. Use SidebarNavItem for workspace-level navigation; keep labels short and reserve shortcut hints for repeated operator actions.
3. Place stat cards above the table only when they summarize live operational state; do not turn them into decorative cards.
4. Use the data-table pattern for repeated run/session rows, preserving tabular numerals, status pills, and a refresh affordance.
5. Wire the command palette to the same action set as visible controls so keyboard and pointer flows stay equivalent.

# Adopt agent dashboard shell

Build a authenticated app dashboard using the components showcase adoption recipe `agent-dashboard-shell`.

## Intent
A dense operational home surface for agent runs, queues, metrics, and fast command entry.

## Component sources
- shells: shell primitives (src/components/shells)
- sidebar-nav: sidebar nav (src/components/sidebar-nav)
- stat-cards: stat cards (src/components/stat-cards)
- data-table: data table (src/components/data-table)
- command-palette: command palette (src/components/command-palette)

## Style sources
- components: components — default (@creative-int/design)
- luke: luke — slate-core + holo (apps/luke)

## Implementation steps
1. Start with HeaderShell or SidebarHeaderShell so navigation, page title, and primary actions share one stable chassis.
2. Use SidebarNavItem for workspace-level navigation; keep labels short and reserve shortcut hints for repeated operator actions.
3. Place stat cards above the table only when they summarize live operational state; do not turn them into decorative cards.
4. Use the data-table pattern for repeated run/session rows, preserving tabular numerals, status pills, and a refresh affordance.
5. Wire the command palette to the same action set as visible controls so keyboard and pointer flows stay equivalent.

## Acceptance checks
- dashboard shows at least one navigation rail, one metric group, one tabular list, and one command entry path
- all surfaces read semantic tokens from @creative-int/design or the selected style bundle
- table rows stay scannable at mobile and desktop widths without text overlap
- keyboard users can open the command flow and reach the primary table action
- proof covers the dashboard route plus /data-table and /styles/components as reference routes

## Proof routes
- /adoption/agent-dashboard-shell
- /data-table
- /styles/components

acceptance

• dashboard shows at least one navigation rail, one metric group, one tabular list, and one command entry path
• all surfaces read semantic tokens from @creative-int/design or the selected style bundle
• table rows stay scannable at mobile and desktop widths without text overlap
• keyboard users can open the command flow and reach the primary table action
• proof covers the dashboard route plus /data-table and /styles/components as reference routes

artifact