Dashboard Overview
The screen an app opens on: shell, header, KPI row, chart and activity feed — numbers first, shape second, changes last.
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.
app/first-run-page.tsxnpx hoverlab add first-run-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.
The tour, the loading state everything is in while it runs, and the one thing that survives both.
Rows of whatever this product shows sit here. The tour points at the controls above without moving the reader away from them.
Filters stack, and every one you apply stays visible as a chip above the results so you always know why you are seeing what you are seeing.
1 of 4
Five short steps and your workspace is ready to use.
Create your account
Done — welcome aboard.
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 Onboarding.
/**
* The first ninety seconds, which is the only part of onboarding most
* people see.
*
* `onboarding-page` is the guided version — a checklist, a role, an import.
* This is what the product looks like *while* that is happening, and it is
* three states nobody designs because none of them are the product.
*
* coachmark a tour step anchored to the control it explains, with the
* spotlight cut by a single spread shadow. Anchored, not
* floating: a tour that describes a button without pointing
* at it is a slideshow, and people close slideshows
* skeleton the placeholders, with a sweep that is motion-safe only.
* First run is the slowest the product will ever be — every
* cache is cold — so this is the state most likely to be
* someone's first impression of the interface
* checklist the progress they came here to make
*
* The checklist is shared with `onboarding-page` on purpose, and it is the
* only block on this page that also appears elsewhere. That is the join
* between the two screens: the tour and the skeletons are transient, the
* checklist persists, and seeing it in both places is how a reader works
* out that first-run is a state of the app rather than a separate flow.
*/
import * as React from 'react'
import { ProductTourCoachmark } from '@/components/product-tour-coachmark'
import { SkeletonList } from '@/components/skeleton-list'
import { OnboardingChecklist } from '@/components/onboarding-checklist'
export default function FirstRunPage() {
return (
<main className="min-h-screen bg-background text-foreground">
<section className="mx-auto w-full max-w-5xl px-6 pb-2 pt-12">
<h1 className="text-2xl font-bold tracking-tight">First run</h1>
<p className="mt-1 text-sm text-muted-foreground">
The tour, the loading state everything is in while it runs, and the
one thing that survives both.
</p>
</section>
<ProductTourCoachmark />
<SkeletonList />
{/* Shared with onboarding-page — see the note above. */}
<OnboardingChecklist />
</main>
)
}
components/ — each block page has its own copy button.app/first-run-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.
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.
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.