Dashboard Overview
The screen an app opens on: shell, header, KPI row, chart and activity feed — numbers first, shape second, changes last.
The furniture that is on every screen and belongs to none — navbar, mobile drawer, command palette, shortcut sheet, header search, scope switcher, and the two shapes a detail view takes without losing the list.
app/app-shell-page.tsxnpx hoverlab add app-shell-page
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
You are viewing Northwind as priya@meridianfoods.com. Anything you do here is recorded against your own name.
The furniture: navigation, the two keyboard surfaces, search, and the two ways to open a detail view without losing the list.
Actions
Navigation
Nothing matched. Press Enter to search everything for “meri” anyway.
0 suggestions. Enter searches for what you typed.
Results for “renewal”
…the renewal window opens 60 days before the term ends, and the owner…
Updated 3 days ago · Sam Okafor
……what happens at renewal if the seat count changed mid-term?
Updated 2 weeks ago · Rhea Patel
…Renewals lead · jordan@acme.com
Customer Success
…Rhea: pushing the renewal call to Thursday, they want the usage report first
14 replies · yesterday
The real page, rendered in your current theme — every section below is a live block, not a screenshot.
Only want one section? Open it and copy that block instead — browse Navigation.
/**
* The chrome around an application: everything that is on every screen and
* belongs to none of them.
*
* This page is a deliberate exception to how the rest of the catalog is
* organised. The other pages are places; this one is the furniture. It
* exists because navigation and overlay components are the ones most often
* built twice — once well in the design system and once badly in a hurry —
* and seeing the eight of them together makes the duplication obvious.
*
* Grouped by how a person reaches them:
*
* pointer navbar, mobile drawer
* keyboard command palette, and the "?" sheet that teaches it
* search the field in the header, and one query counted across
* every scope it could have matched
* surfaces bottom sheet, slide-over — the two shapes a detail view
* takes when it must not lose the list behind it
*
* The distinction between <CommandPalette> and <SearchAutocomplete> is the
* reason both are here. They look identical and behave oppositely: the
* palette is a switcher where Enter runs the highlighted command, and the
* header field is a search where Enter searches for what you *typed* unless
* you arrowed down first. Shipping one with the other's Enter behaviour is
* a bug that survives review because the screenshot is the same.
*
* <KeyboardShortcutsSheet> is placed right after the palette rather than at
* the end, because a keyboard interface nobody can discover is a keyboard
* interface nobody uses, and the sheet is the discovery mechanism.
*/
import * as React from 'react'
import { NavbarAuthenticated } from '@/components/navbar-authenticated'
import { NavMobileDrawer } from '@/components/nav-mobile-drawer'
import { CommandPalette } from '@/components/command-palette'
import { KeyboardShortcutsSheet } from '@/components/keyboard-shortcuts-sheet'
import { SearchAutocomplete } from '@/components/search-autocomplete'
import { SearchScopeSwitcher } from '@/components/search-scope-switcher'
import { BottomSheetMobile } from '@/components/bottom-sheet-mobile'
import { SlideOverPanel } from '@/components/slide-over-panel'
export default function AppShellPage() {
return (
<main className="min-h-screen bg-background text-foreground">
<NavbarAuthenticated />
<section className="mx-auto w-full max-w-5xl px-6 pb-2 pt-10">
<h1 className="text-2xl font-bold tracking-tight">App shell</h1>
<p className="mt-1 text-sm text-muted-foreground">
The furniture: navigation, the two keyboard surfaces, search, and
the two ways to open a detail view without losing the list.
</p>
</section>
<NavMobileDrawer />
<CommandPalette />
<KeyboardShortcutsSheet />
<SearchAutocomplete />
<SearchScopeSwitcher />
<BottomSheetMobile />
<SlideOverPanel />
</main>
)
}
components/ — each block page has its own copy button.app/app-shell-page.tsx. The imports already point at @/components/…, so they resolve with no edits.The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
The screen an app opens on: shell, header, KPI row, chart and activity feed — numbers first, shape second, changes last.
An agent working inside a real app: a transcript down the middle — reasoning, answer, then the one card that can act — with what it may read and what it noticed demoted to a rail.
A kanban board inside the app shell, with tabs that admit the board is one view among several and a header whose primary action is creating work.
The canonical CRUD list — header, toolbar, sortable table and pagination framed as one panel instead of three stacked cards.
A wizard for the session someone finishes and a checklist for the one they do not, with the only genuinely blocking step in front of both.
Built around the state a search page is in most of the time — empty — so recent queries lead and the facets sit in a sidebar that survives growing to twelve.
One run opened up in the order you would debug it — intent, actions, the retries that are invisible in both, then cost.
The queue, the same queue sorted by how long things have waited, and the policy that decided both — with the policy last so it is not scrolled past forever.
The blank thread answered with real starter prompts, the model picker with the three numbers the choice turns on, and the four surfaces a session grows into — attachments, branches, canvas, threads.
The three states an agent screen usually omits: the wait before the first token, the trace after something broke with retries costed in the open, and the diff it wants a person to accept.
Why the answer said what it said: what is connected, how stale it is, what the query was allowed to see, what fitted in the window and what fell out — plus the failed-search state a debugging tool is most needed in.
Five ways to reach a model without the cursor leaving the sentence — slash menu, inline completion, selection toolbar, action menu, property inspector — and the two surfaces that say where the answer came from.
A table after real people have used it — columns reordered from the keyboard, a selection bar that asks page-or-all, subtotals that survive collapsing, cells edited in place, and the empty state its own filters produced.
The saved view and the comparison window first, because every figure below depends on both — then six charts, none of which load a charting library.
Thresholds with how often each has actually fired, what that produced, where it went — and the digest settings that exist because of the answer.
The flow between an empty product and a useful one, in the order it goes wrong: sample data offered with equal weight, a file, a URL, the column mapping everything stalls on, and an upload that survives the connection dropping.
A profile form where the role options state what they actually change, the avatar crop works from the keyboard, and a navigation guard names the fields it is about to throw away.
Backwards from now and forwards from it on one screen — a day-grouped timeline, a month grid where a busy Tuesday never changes the row height, and the state both are in on day one.
What the product looks like while onboarding happens: a tour step anchored to the control it explains, the skeletons of the slowest load it will ever do, and the checklist that outlives both.