- Adopt
- Trial
- Assess
- Hold
- New
AdoptOur default. We reach for this without a discussion.
- 17
Playwright
End-to-end tests, visual checks and the odd build-time screenshot run through one API. It also drives the renderer that produces this site’s showreel.
- 18
GitLab CI
Pipelines live in the repository and run on the client’s own runners, which is what makes handover a permissions change rather than a migration.
- 19
Lightning CSS
Bundling, minification and transpiling of modern CSS with no plugin chain. Read its shorthand-folding rules before writing scroll-driven animation.
- 20
Drizzle Kit
Migrations generated from the schema and then committed as plain SQL. What runs in production is a file we reviewed, not a diff computed at deploy time.
TrialRunning in production on at least one project.
- 21
Storybook
The review surface for shared components, so a state can be looked at without routing to a page that produces it. Earns its keep once components are reused.
- 22
Infisical
Self-hostable secret management with per-environment scoping. Chosen over a hosted vault because the client keeps the instance.
- 23
better-authNew
Sessions, OAuth and organisation membership as tables in our own database rather than a third-party user directory. Good so far on one production system.
AssessWorth the time to understand. Not in client work yet.
- 24
Lighthouse in CI
A budget that fails the pipeline is more honest than a score checked before launch and never again. We are still choosing thresholds we would actually enforce.
Next step
Tell us what
you need built
Send the idea in whatever shape it is in — a document, a sketch, or two sentences. You get a written scope and a fixed figure back before anything is committed to.