mock-up
Builds a static, clickable mock-up of the client’s system in mock-up/ —
desktop, iPhone, and iPad layouts, light and dark mode, their logo and colors,
and 30 days of believable mock data.
Invocation
Section titled “Invocation”/mock-up/mock-up café POS with inventory for 3rd Space, logo in ./brand/logo.svgWhat it does
Section titled “What it does”- Reads what you already gave it, then asks two short rounds of questions: the client and their process, then devices, theme, accent, and extras.
- Proposes a blueprint — 4 main tabs, up to 6 bubble functions, the key flows, the mock data, and 2–3 demo moments — and waits for your yes.
- Copies its app shell into
mock-up/and builds every screen and flow. - Screenshots every route with headless Chrome, fixes what it finds, and looks at the result.
- Writes
mock-up/README.mdand hands you a 5–7 step demo script.
What it guarantees
Section titled “What it guarantees”- Nothing is written before you approve the blueprint.
- Every button does something, and every action shows up elsewhere: history, dashboard, and audit trail.
- The data is clearly mock data, never real customer or patient records.
- It never commits, pushes, or deploys. Publishing the demo to Vercel needs a separate yes from you.
- It writes no
syntaxis/workflow files.
Present the demo, then /quote when the client asks
what it costs. See Building a Mock-up.