Skip to content

Building a Mock-up

/mock-up builds a demo a client can actually click through: their logo and colors, their vocabulary, their process, on desktop, iPhone, and iPad, in light and dark mode. Every button works, and every action shows up elsewhere — a sale lands in the order history, the dashboard, and the audit trail.

It’s a static site in mock-up/ with no build step, no framework, and no backend, so it opens from a folder and deploys to Vercel in one command.

Have whatever you already know about the client to hand. Anything you give up front is never asked again.

  • The business and what the system is: “café POS with inventory”, “dental clinic appointments”, “school enrollment portal”.
  • Who uses it: owner, manager, cashier, receptionist, and so on.
  • The process, step by step, including approvals (“refunds need a manager”).
  • The brand: colors, fonts, mood, and the logo file if there is one.
  • Locale: country, currency, language.

For the self-check you need Node.js 22 or newer and Google Chrome or Chromium. Without Chrome the build still happens; the agent syntax-checks the code and asks you to open the preview yourself. Nothing gets installed.

/mock-up
/mock-up café POS with inventory for 3rd Space in Manila, logo in ./brand/logo.svg
/mock-up clinic booking demo, just go with defaults

First a plain message with up to six open questions — project, client needs, process, branding, logo, locale — skipping anything you already answered. Then four quick choices:

Choice Recommended default
Devices Desktop + iPhone + iPad
Default theme Light, with dark included
Accent color Derived from the brand, with the reason given
Extras Audit trail, roles with manager PIN approvals, reports with CSV export

Say “just go” and it skips the questions, then lists its assumptions in the blueprint instead.

The phone layout forces a real decision, so the agent makes it up front: exactly four main tabs for the most frequent daily tasks, plus up to six bubble functions for back-office work. The bubbles fan out from a logo button in the middle of the phone’s tab bar, closest to the thumb first.

A café POS blueprint might look like this:

Main tabs Home · Register · Orders · Inventory
Bubbles Cash & Shifts · Reports · Customers · Audit Trail · Staff · Settings
Key flows Drink → options → cart → pay → receipt → bar queue; refund with manager PIN; receive stock → sold-out item returns
Mock data Menu with recipes, ~3,400 orders over 30 days, shifts, suppliers
Demo moments Selling a latte deducts beans and milk; a barista’s refund asks for a manager PIN; the brand color changes live

Nothing is written until you say Build it. You can change the tabs, bubbles, features, or flows first.

The agent copies its app shell into mock-up/ and builds on it:

mock-up/
├── index.html
├── vercel.json static hosting config, ready as-is
├── README.md written at hand-off
├── assets/ logo and favicon
├── css/
│ ├── app.css shared shell — not edited per client
│ ├── patterns.css shared screen patterns
│ ├── device.css iPhone / iPad preview frames
│ └── views.css this client's own styles
└── js/
├── config.js name, locale, currency, accent, tabs, roles
├── data.js the deterministic mock-data generator
├── domain.js business actions, each one audited
├── brand.js the logo mark
└── views/ one file per screen

The mock data is seeded from the date, covers the last 30 days up to now, and regenerates each new day, so the dashboard never looks stale. It’s linked — orders point at customers and staff — so reports add up, and it includes the awkward cases (refunds, no-shows, low stock) that give status badges something to show. It’s always invented, never real customer or patient records.

The bundled script serves the folder, drives headless Chrome, and screenshots every route on desktop, in dark mode, on iPhone with the bubble menu open, and on iPad in both orientations. It fails on console errors, failed requests, and horizontal overflow on a phone — the most common responsive bug. The agent then looks at the screenshots, because a script can’t judge design, and clicks through each key flow on desktop and iPhone.

You get mock-up/README.md, a summary of what was built, the assumptions to confirm (invented names, placeholder legal details), and a 5–7 step demo script: the order to click things in front of the client, ending on the “wow” moments.

Open it locally:

Terminal window
npx serve mock-up
  • Device preview: the Desktop / iPhone / iPad switch in the top bar shows the phone and tablet layouts in a device frame, on your laptop.
  • Roles: the user card in the sidebar switches who is signed in. The demo PIN for manager approvals is 1234.
  • Theme: the toggle in the top bar, or Settings.
  • Fresh start: Settings → Reset data, keep branding, or Reset everything.

The demo is Vercel-ready:

Terminal window
cd mock-up && vercel --prod

Or import the repository on Vercel with the framework preset Other, no build command, and output directory .. The agent prepares this but never deploys on its own: publishing a client’s demo to the internet needs your explicit yes in the same chat.

For small changes, ask in the same chat: “make the accent darker”, “add a Loyalty bubble”, “rename Covers to Guests”. Running /mock-up again on an existing folder asks whether to overwrite it or build alongside it as mock-up-<slug>/.

  • Write anything before you approve the blueprint.
  • Use real personal data, even if the client offers some.
  • Commit, push, or deploy.
  • Install a browser or any dependency.
  • Read or write the Syntaxis plans, specs, or findings.

When the client asks what the real thing costs, run /quote.