BoilerPrompt
Bolt

Bolt prompt for a 404 page

A single-viewport 404 for Bolt with a fake command line that types "searching for page... 0 results", then routes whatever you type into real search. Explicit error labeling comes before the humor, and a referrer strip offers a way back to where you came from. Style, palette, typography, and motion are customizer-driven, so the bit lands in any brand.

Last updated

Prompt
Create a standalone 404 page for {{product}} in this project — one file at src/pages/NotFound plus a catch-all route entry, styled to feel deliberate rather than default. Its job: tell {{audience}} they're off the map and hand them a way back within five seconds.

Structure, one full-viewport column, vertically centered:
1. Status line — small uppercase label reading "Error 404 — page not found", so the state is explicit before any humor starts.
2. Headline — one memorable sentence riffing on {{product}}'s domain (ask yourself what "lost" means inside this product's world); ten words maximum.
3. The interactive touch — a fake command line beneath the headline that types out "searching for page... 0 results" once on load, then blinks a cursor; typing text and pressing Enter routes to the search page with the query prefilled.
4. Recovery actions — the primary button plus two secondary links: homepage and support.
5. Baseboard — a thin strip at the bottom naming the last-visited page (read document.referrer; hide the strip when it's empty) with a "take me back" link.

Visual direction:
{{style}}

Palette: {{palette}}
Typography: {{type}}
Motion: {{motion}}

Spacing and responsive:
- Center the column with flex and cap content width at 560px; vertical gaps run 16px within a group and 48px between groups.
- Under 480px, skip the typing animation and render the command line's final state statically, so small devices avoid the animation and any keyboard-trap weirdness.

The primary call to action is "{{cta}}".

Watch the preview and verify before finishing: the typing animation runs exactly once and never loops; pressing Enter with typed text navigates to /search?q= plus the text; the referrer strip is hidden when the page is opened directly; there is no vertical scrollbar at 1440x900; the column still centers at 360px wide.

Customize it

Runs in your browser. Nothing you type here is sent anywhere.

Your customized prompt
Create a standalone 404 page for a project management SaaS in this project — one file at src/pages/NotFound plus a catch-all route entry, styled to feel deliberate rather than default. Its job: tell engineering managers at startups they're off the map and hand them a way back within five seconds.

Structure, one full-viewport column, vertically centered:
1. Status line — small uppercase label reading "Error 404 — page not found", so the state is explicit before any humor starts.
2. Headline — one memorable sentence riffing on a project management SaaS's domain (ask yourself what "lost" means inside this product's world); ten words maximum.
3. The interactive touch — a fake command line beneath the headline that types out "searching for page... 0 results" once on load, then blinks a cursor; typing text and pressing Enter routes to the search page with the query prefilled.
4. Recovery actions — the primary button plus two secondary links: homepage and support.
5. Baseboard — a thin strip at the bottom naming the last-visited page (read document.referrer; hide the strip when it's empty) with a "take me back" link.

Visual direction:
Minimal dark style. Near-black canvas (#0A0A0B) with one elevated surface tone (#141416) for cards — never more than two surface steps. Hairline borders (1px, white at 8% opacity) instead of shadows; if a shadow is unavoidable use 0 1px 2px rgba(0,0,0,0.4) and nothing softer. Text in exactly three steps: white at 92% for headings, 60% for body, 40% for captions. Generous negative space — section padding at least 120px on desktop, 64px on mobile. The accent color appears only on interactive elements and one hero highlight, nowhere else.

Palette: a strict neutral ramp (white, #F5F5F5, #E5E5E5, #737373, #171717) carries the entire interface; pick one accent and use it only for primary CTAs, active states, and a single hero highlight. If the accent appears more than five times per viewport it stops being an accent. Keep semantic colors (success, error) desaturated so the accent stays in charge.
Typography: one geometric sans (a Futura/Poppins-class face) at three weights maximum (400/500/700). Scale: 64-88px hero, 32px section heads, 18px lede, 16px body, 13px caps labels with 0.08em tracking. Tight headline leading (1.05-1.1), relaxed body (1.6). Let the geometry carry the personality — no italics; weight and size do all hierarchy.
Motion: none. Zero scroll animations, zero entrance effects — the page is fully composed the instant it paints. Spend the motion budget on input feedback instead: 120-150ms ease-out color and transform transitions on hover and press states only. Hold this constraint absolutely; it is a statement, not an omission.

Spacing and responsive:
- Center the column with flex and cap content width at 560px; vertical gaps run 16px within a group and 48px between groups.
- Under 480px, skip the typing animation and render the command line's final state statically, so small devices avoid the animation and any keyboard-trap weirdness.

The primary call to action is "start a free trial".

Watch the preview and verify before finishing: the typing animation runs exactly once and never loops; pressing Enter with typed text navigates to /search?q= plus the text; the referrer strip is hidden when the page is opened directly; there is no vertical scrollbar at 1440x900; the column still centers at 360px wide.

Same task in other tools

Questions about this prompt

Can I drop the fake command line entirely?

Yes — delete step 3 from the structure list before pasting and move search into the recovery actions row as a plain input. The rest of the page doesn't reference the terminal bit, so nothing else needs rewording.

My site has no /search route — where should typing route to?

Point it anywhere that can absorb a query: your docs search, a Google site: search URL, or simply make Enter go home. Change the destination in the structure list and in the matching verification item so Bolt confirms the right behavior.

How do I move this page into my real project afterwards?

It's one page file plus a route entry, so copy src/pages/NotFound into your app and register it as the catch-all in your router. Serve it with an actual 404 status from your host or framework config — Bolt's preview won't enforce that part for you.

Part of the Bolt landing-page cluster — start from the main Bolt landing page prompt.

Related prompts