Skip to content

First Run

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.

3 blocks50 lineslucide-reactAdded 10 Sept 2026

What's included

  • app/first-run-page.tsx
  • 3 blocks it is built from, installed with it
  • Needs lucide-react

Works with

  • React
  • Next.js
  • Tailwind CSS
  • TypeScript

npx hoverlab add first-run-page

Or over MCP, from your editor's agent — no account needed.

License

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.

Was this useful?

Preview

First run

The tour, the loading state everything is in while it runs, and the one thing that survives both.

FiltersSearchExportInvite

Rows of whatever this product shows sit here. The tour points at the controls above without moving the reader away from them.

Loading

Finish setting up

Five short steps and your workspace is ready to use.

1 of 5
  • Create your account

    Done — welcome aboard.

  • Create your first project

    A project holds your environments, keys and deployments.

    Start2 min
  • Install the CLI

    One command, and your terminal can deploy.

    Start3 min
  • Invite a teammate

    Projects are more useful with someone to share them with.

    Start1 min
  • Connect a domain

    Point a hostname at your first deployment.

    Start5 min

The real page, rendered in your current theme — every section below is a live block, not a screenshot.

Built from

All blocks
  1. Product Tour Coach MarkA tour step anchored to the control it explains, with a spotlight cut by one spread shadow, a visible step count and focus that follows the step.
  2. Shimmer Skeleton ListLoading placeholders with varied row widths and a sweep that is motion-safe only, falling back to a flat tint under reduced motion.
  3. Setup Checklist with ProgressThe get-started card that ships with its first item already ticked, a native <progress> element rather than a div bar, and a dismiss control that appears only once there is nothing left to abandon.

Only want one section? Open it and copy that block instead — browse Onboarding.

Source

app/first-run-page.tsx
/**
 * 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>
  )
}

How to use it

  1. 1. Copy each of the 3 blocks above into components/ — each block page has its own copy button.
  2. 2. Drop this file at app/first-run-page.tsx. The imports already point at @/components/…, so they resolve with no edits.
  3. 3. Delete the sections you do not want. Every block takes props, so the copy changes without the layout moving.

For AI

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.

See the prompt

More App Screens

Open the full page for this page

Dashboard Overview

The screen an app opens on: shell, header, KPI row, chart and activity feed — numbers first, shape second, changes last.

App Screens5 blocks47 lines
Open the full page for this page

AI Assistant Screen

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.

App Screens7 blocks110 lines
Open the full page for this page

Project Board

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.

App Screens3 blocks42 lines
Open the full page for this page

Customer List Screen

The canonical CRUD list — header, toolbar, sortable table and pagination framed as one panel instead of three stacked cards.

App Screens5 blocks37 lines
Open the full page for this page

Onboarding

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.

App Screens3 blocks45 lines
Open the full page for this page

Search Results

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.

App Screens4 blocks47 lines
Open the full page for this page

Agent Run Detail

One run opened up in the order you would debug it — intent, actions, the retries that are invisible in both, then cost.

App Screens4 blocks49 lines
Open the full page for this page

Approvals Inbox

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.

App Screens3 blocks45 lines
Open the full page for this page

Assistant Chat

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.

App Screens6 blocks68 lines
Open the full page for this page

Agent Run Inspector

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.

App Screens5 blocks61 lines
Open the full page for this page

Retrieval Console

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.

App Screens7 blocks66 lines
Open the full page for this page

AI Editor

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.

App Screens7 blocks64 lines
Open the full page for this page

Records Table

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.

App Screens8 blocks71 lines
Open the full page for this page

Analytics

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.

App Screens8 blocks68 lines
Open the full page for this page

Alerting

Thresholds with how often each has actually fired, what that produced, where it went — and the digest settings that exist because of the answer.

App Screens5 blocks54 lines
Open the full page for this page

Import Data

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.

App Screens7 blocks64 lines
Open the full page for this page

Account Setup

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.

App Screens4 blocks53 lines
Open the full page for this page

App Shell

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 Screens8 blocks68 lines
Open the full page for this page

Workspace Activity

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.

App Screens3 blocks51 lines