GOV.UK Prototype Kit vs Vibe.WithGov
Both produce Nunjucks + Express prototypes. The difference is who writes the code, and how fast you get to a journey a researcher can click.
- Updated
- May 2026
- 6 min read
The GOV.UK Prototype Kit is the canonical government-built toolchain for rapid prototyping: a Node.js + Nunjucks project published by the Government Digital Service, used by service teams across UK departments to build clickable journeys for user research. Vibe.WithGov is an independent tool that generates a Prototype Kit project from a plain-English service spec.
Both produce the same kind of artefact: a Node + Nunjucks app using GOV.UK Design System components. The difference is who writes the code. With the Kit you write the Nunjucks templates, Express routes and validation by hand. With Vibe you describe the journey (“an applicant applies for a fishing licence: name, address, date of birth, licence type, payment”) and the same artefact is generated for you.
The matrix
Grouped by the question each row answers, not by alphabetical feature. Categories are colour-coded so the eye can navigate by section rather than scanning every cell.
Vibe.WithGov
AI generates a Prototype Kit project from a plain-English spec.
GOV.UK Prototype Kit
The GDS-published Node + Nunjucks toolchain.
Time to a first clickable journey
Front-end skill required
Iterate by conversation
Type a change in plain English; the AI rewrites the affected templates and routes.
GOV.UK Design System components
Nunjucks templates + Express routes
Server-side validation wired to error summary
Branching journeys / eligibility flows
WCAG 2.1 AA on first paint
Affiliated with GDS
The Kit is published by the Government Digital Service. Vibe is independent.
Live preview while iterating
Share with research participants
Export the code
Hosting & infra
Cost
Time to a first clickable journey
Vibe.WithGov
Seconds, from one plain-English specGOV.UK Prototype Kit
Hours to days of hand-codingFront-end skill required
Vibe.WithGov
NoneGOV.UK Prototype Kit
Working Nunjucks + ExpressIterate by conversation
Vibe.WithGov
SupportedGOV.UK Prototype Kit
Not supportedType a change in plain English; the AI rewrites the affected templates and routes.
GOV.UK Design System components
Vibe.WithGov
SupportedGOV.UK Prototype Kit
SupportedNunjucks templates + Express routes
Vibe.WithGov
SupportedGOV.UK Prototype Kit
SupportedServer-side validation wired to error summary
Vibe.WithGov
Generated from the specGOV.UK Prototype Kit
Hand-rolled per routeBranching journeys / eligibility flows
Vibe.WithGov
Described in proseGOV.UK Prototype Kit
Coded by hand
WCAG 2.1 AA on first paint
Vibe.WithGov
Semantic headings, focus states, error summaries by defaultGOV.UK Prototype Kit
Available; author wires themAffiliated with GDS
Vibe.WithGov
Not supportedGOV.UK Prototype Kit
SupportedThe Kit is published by the Government Digital Service. Vibe is independent.
Live preview while iterating
Vibe.WithGov
Per-project sandbox URL, hot-reloadGOV.UK Prototype Kit
Run locally with `npm start`Share with research participants
Vibe.WithGov
Unguessable sandbox URLGOV.UK Prototype Kit
Deploy yourself (Heroku, fly.io, etc.)Export the code
Vibe.WithGov
ZIP + GitHub push from the editorGOV.UK Prototype Kit
Your local editor + gitHosting & infra
Vibe.WithGov
Managed; UK data residency by defaultGOV.UK Prototype Kit
You host it
Cost
Vibe.WithGov
Free tier; paid plans from £19/moGOV.UK Prototype Kit
Free (MIT-licensed open source)
When the Prototype Kit is the right call
- Your team already has a developer who knows the Kit, and the journey you need is small enough that hand-coding it is faster than briefing a tool.
- You need full control over the Nunjucks output for an unusual pattern that isn’t in the design system.
- You want a tool the GDS itself publishes and maintains, with no third-party dependency in your discovery process.
- You want to extend the Kit with custom middleware, integrate with internal department APIs at the prototype stage, or run it inside an air-gapped environment.
When Vibe is the right call
- The team is a service designer or product manager with no dedicated front-end developer to hand the spec to.
- You need a working journey in front of research participants this week, not next sprint.
- You are exploring two or three competing service designs and want a real clickable comparison rather than wireframes.
- You want the validation, error summary and accessibility patterns wired up correctly the first time, without having to remember which Design System rule applies where.
- You want the prototype on a shareable URL without standing up your own Heroku or fly.io instance.
Can the two be used together?
Yes. The Vibe output is a Prototype Kit project. You can export it as a ZIP, open it in your editor and continue building in the Kit by hand. A common pattern: generate the first three or four pages of a journey in Vibe to get to a clickable artefact quickly, then drop into the Kit to refine specific pages with unusual interaction patterns. The hand edits round-trip back into Vibe so the AI can pick the work up again when you next want to iterate by conversation.
Vibe.WithGov is an independent product. It generates prototypes that follow GOV.UK Design System patterns but is not affiliated with, endorsed by, or part of the Government Digital Service. The GOV.UK Prototype Kit is published by GDS and is the work of the Service Manual team. See the FAQ for more.