The
Arsenal
No percentages, no self-graded proficiency charts. These are the tools I reach for on real projects, organised by how often I actually use them.
Frontend
6 toolsApp Router, RSC, Server Actions — the default for every web build.
Strict mode across every project. The type system is part of the design.
Utility-first with a custom design system layered on top.
For motion systems where I want physics, not just easing curves.
Native iOS UI. Charts, Live Activities, symbol effects on iOS 17+.
When a marketing site needs scroll-driven choreography, not just reveals.
Backend
6 toolsFastAPI for APIs. Playwright for crawlers. Pandas where the data lives.
API routes, background workers, serverless functions.
Relational data with deliberate schema design, not auto-generated blobs.
Postgres + Auth + Storage + Edge Functions — default BaaS for small teams.
Caching, queues, rate limits, session storage.
For pipelines that need to run the same on my laptop and in CI.
AI / ML
5 toolsPrompt design, function calling, structured outputs, embeddings.
Primary for cost-sensitive draft generation (used in LeadSniper).
For agent loops and retry-aware chains — not for simple prompts.
Vector search + retrieval over domain docs, not generic wrappers.
Google Cloud STT for non-English; Whisper for offline contexts.
Infra & DevOps
4 toolsDefault host for Next.js work. Preview deploys on every PR.
Tests, builds, and deploys — everything that shouldn't be manual.
Used where the client already lives; not my default for greenfield.
Headless browsers for scraping, e2e tests, and visual diff.
Currently Learning
Rust
Systems-level reach when Python is the bottleneck.
Kubernetes
For stacks that outgrow a single-VM footprint.
Three.js / WebGL
Real-time 3D on the web — product visualisations and interactive demos.
Solidity
Smart contracts — selectively, where on-chain is genuinely the right fit.
Need this stack
on your team?
Every tool here has been used on at least one shipped project. Let me put them to work on yours.
Let's Build →