Bolt Prompts

Bolt (bolt.new by StackBlitz) is the tool when you want the whole stack in one sandbox — frontend, backend, database, running in the browser. Its failure mode is scope drift: ask vaguely and you get an impressive-looking app with three unrequested features and no delete confirmation. These prompts pin the scope down: exact views, exact endpoints, seed data, "keep the code boring".

Best use: validating a workflow with real data by tomorrow — MVPs, internal tools, API prototypes for client demos.

Bolt 65 words

Full-Stack CRUD MVP in One Shot

Bolt's differentiator: the whole stack runs in one browser sandbox.

Build a full-stack <resource> tracker (e.g. expenses, tasks, clients): React frontend with list view, create/edit modal and delete confirm; Express + SQLite backend with REST CRUD endpoints; simple stats row on top (total, count, latest). Seed 5 demo rows. Run entirely in-browser, no external services. Keep files small and the code boring — this is an MVP to validate the workflow, not a portfolio piece.

Bolt 60 words

Admin Table with Search, Filter, Pagination

The internal-tool pattern every company needs and nobody wants to build.

Build an internal admin page for managing <resource>: data table with search box, a status filter dropdown, column sorting, 10-per-page pagination and row count display; each row has Edit (opens a side drawer form) and Archive (with confirm). Header shows totals per status. Use mock data of 30 rows with realistic values. Prioritize desktop layout, keyboard-friendly (Enter saves, Esc cancels).

Bolt 52 words

Mobile-First PWA Starter

Bolt handles the manifest/service-worker plumbing well.

Build a mobile-first habit tracker PWA: bottom tab navigation (Today, Habits, Stats); Today view with checkable habit cards and a streak flame per habit; Habits view with add/edit/delete; Stats view with a simple 7-day completion bar chart. Installable (manifest + icons), works offline with local storage persistence. Dark mode default. No backend.

Bolt 65 words

REST API Prototype with Docs Page

The docs page makes the prototype demo itself.

Build an Express REST API for <resource> with: CRUD endpoints, input validation returning proper 400s, 404 for missing ids, CORS enabled; plus a single-page docs view at '/' listing every endpoint with method, path, params, and a 'Try it' button that fires the request and shows the JSON response. Seed sample data. This prototype is for showing a client tomorrow — make error messages human-readable.