Skip to content

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.

8 blocks68 lineslucide-reactAdded 10 Sept 2026

What's included

  • app/app-shell-page.tsx
  • 8 blocks it is built from, installed with it
  • Needs lucide-react

Works with

  • React
  • Next.js
  • Tailwind CSS
  • TypeScript

npx hoverlab add app-shell-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

You are viewing Northwind as priya@meridianfoods.com. Anything you do here is recorded against your own name.

App shell

The furniture: navigation, the two keyboard surfaces, search, and the two ways to open a detail view without losing the list.

Acme
esc

Actions

Navigation

navigateselect6 results
Search for meri

Nothing matched. Press Enter to search everything for “meri” anyway.

0 suggestions. Enter searches for what you typed.

Results for “renewal”

Edit customer

Changes apply immediately and are visible to everyone on the team.

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

Built from

All blocks
  1. Signed-in Application BarThe bar above an app rather than a site: workspace and environment named in the open, a bell that counts in words, and an impersonation strip that cannot be dismissed.
  2. Mobile Nav DrawerA slide-in site menu that behaves like a dialog: focus trap, focus restoration, body scroll lock and a transition that drops under prefers-reduced-motion.
  3. Command PaletteThe ⌘K switcher done properly: focus stays in the input while aria-activedescendant moves, arrows wrap, and the highlight resets on every query change.
  4. Keyboard Shortcuts SheetThe "?" overlay, with chords written once in one notation and rendered per platform — mod becomes Command on Apple and Ctrl everywhere else, decided after mount so the markup never mismatches.
  5. Header Search with SuggestionsThe field in the header, not the palette over it: Enter searches for what you typed unless you arrowed to a suggestion, late responses are dropped by sequence number, and recent searches are removable one at a time.
  6. Search Scope SwitcherOne query counted across every scope it could have matched, as a real tablist with arrow-key movement — so an answer that is nowhere is visible without opening four tabs.
  7. Mobile Bottom SheetHalf and full snap points where the content owns the scroll and overscroll-contain keeps the page behind still. The drag handle is a real button, Escape and the backdrop close it, and safe-area padding keeps the last row pressable.
  8. Slide-Over Edit PanelA side sheet for editing a record without losing the list behind it — native <dialog> for the trapping, a data attribute for the slide, and a sticky footer so Save never scrolls away.

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

Source

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

How to use it

  1. 1. Copy each of the 8 blocks above into components/ — each block page has its own copy button.
  2. 2. Drop this file at app/app-shell-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

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

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.

App Screens3 blocks50 lines