Prompt to Page
Status: Beta2026 – · Founder, product and engineering · Tauri 2, TypeScript, llama.cpp, Apple MLX
The problem
Government design teams prototype in code because that is what the design systems are built in. Most of the people who need a prototype — policy leads, content designers, service owners — cannot write it. So the gap between "we need to test this journey next week" and a page a user can react to is filled by a queue for a front-end developer, or by a mock-up that does not behave like the real thing.
The obvious fix is a hosted AI service. In government that fails at the first question: where does the brief go? Policy in draft, user research notes, unreleased service names — none of it should leave the device.
What it does
Prompt to Page runs a language model on your own laptop. You describe the page or journey in plain English; it produces HTML that conforms to the selected design system, checks its own output, and hands you something you can put in front of a user or a developer.
Your brief, your pages and the model stay on your device. There is no account and no API key, and once the model is set up, generating needs no internet connection. The only usage data is two app start and exit events, which are off by default and sent only if you switch them on.
What has shipped
| Area | Status |
|---|---|
| Platforms | macOS (Apple Silicon) and Windows; free public beta |
| Design systems | GOV.UK, NHS.UK, MOJ overlay, USWDS, Scottish Government, NSW, Bootstrap Italia, Japan's DADS (quality not yet measured), and a brand-neutral abstract system |
| Models | Supported on-device models behind per-model quality gates, spanning 8–32 GB of RAM; a 24B premium model gated to 32 GB machines after memory-fault testing |
| Quality | Per-page quality report; automatic repair of two systematic model errors; NHS.UK "quality unknown" caveat removed only after six models were measured at or above their GOV.UK level (v0.3.0) |
| Editing | The HTML view is an editor, not a preview |
| Handoff | Testable ZIP export with font-stripped frontend assets; Nunjucks handoff is bring-your-own |
Current release: v0.7.x, the accessibility release. Release notes are published on GitHub.
What it deliberately does not do
- It does not bundle restricted fonts. GDS Transport and equivalents are sourced by the user under their own licence via the relevant frontend package. The app never ships them.
- It does not ship protected government marks. Crowns, logotypes and official header/footer examples are stripped from every corpus. Continuous integration scans both source and packaged installers and fails the build if any appear.
- It does not claim conformance it hasn't measured. Each design system carries a quality level, and the level only moves when the evidence does.
- It does not send your work anywhere. Local-first is the architecture, not a setting: prompts and pages never leave the device, and usage events stay off unless you switch them on.
Who it is for
Content designers, interaction designers and product people in public-sector teams who need a realistic page quickly and cannot send their brief to a third party. Early reviewers include practitioners working with the Scottish Government, NSW and Italian government design systems.
How to get involved
The beta is free and public: download it for macOS or Windows. I am looking for practitioners who use one of the supported design systems day to day and will spend twenty minutes building one short journey and telling me what is wrong with it.
If you would rather not install anything, I can send a no-install review packet instead: a recording of a build and the exported source to review.
Feedback is sought from practitioners outside my employing department. Email hello@courtneyallen.co.uk with the design system you work in.
Licensing and source
Prompt to Page is a proprietary beta, licensed not sold, under a published EULA. The public GitHub repository hosts the downloads and the beta terms, not the application source.