Notes from building Prompt to Page.
Working notes on local models, the GOV.UK Design System, accessibility, and what it takes to keep a prototyping tool fully offline.
- 8 min read
To add a second design system, I had to find where the first one was hiding
Adding NHS, HMRC and a genuinely neutral design system forced me to notice that GOV.UK was never logic — it was reference data, quietly hardwired across the codebase.
Read post - 5 min read
Matching an AI model to the machine in front of you
How the app picks a model that fits the user's hardware — and why I'm still unsure whether to hide incompatible premium models or show them, greyed out, with a reason.
Read post - 6 min read
I wrote the counter-arguments before I wrote any code
Why I wrote the counter-case first — and the go/no-go gates that keep a seductive ML idea from becoming an expensive mistake.
Read post - 6 min read
Smaller models need smaller prompts
Trimming worked examples from the prompt took a small model from 1/7 passing test cases to 4/7 — and the average score from 59 to 83.
Read post - 5 min read
Teaching a local model the GOV.UK Design System — without fine-tuning it
How Prompt to Page uses a class list and just-in-time component retrieval to keep a local model's GOV.UK output accurate — without retraining the model.
Read post - 5 min read
The small models got good — and that changes where government AI can run
Open-weight models now fit the government standard laptop. Here's why that changes what AI government teams can actually run on-device.
Read post - 6 min read
I built a GOV.UK prototyping tool that never goes online
Why Prompt to Page runs entirely on your machine — no API keys, no cloud round-trips, and no draft policy leaving the building.
Read post