A designer with no engineering team, running a production platform end to end with agentic development: 51K lines of TypeScript across 11 subsystems, an assistant that runs 29 tools from a phone, and a container that redeploys on every push.
Insert High-Res Hero Mockup
Showcase a beautiful, wide shot of the Flea Market UI Kit.
The Challenge
I did not want another portfolio that sits still and waits to be found. I wanted one that works: auditing sites, tailoring applications, researching leads, and reporting back to me on a phone. That is not a page. That is production software, with state on disk, a queue, a scheduler and a deploy, and everything that can go wrong in each of them.
The honest shape of the problem was this. I could specify all of it, judge whether it was right, and design every screen. I could not sit down and hand-write fifty thousand lines of TypeScript. No off-the-shelf answer solved it either, because no template ships job applications from a chat thread.
So the build became the question worth answering: how far does a designer get by directing AI agents, if the standard is production rather than a demo?
A Page That Waits
Moving Parts
No Team
Off the Shelf
My Approach
I stopped using AI as autocomplete and started treating it as a team that needs a brief and a standard. Architecture written down before the code, the right model picked per job, and a mechanical gate that no change gets past.
The architecture lives in the repo as a document every agent reads before it touches anything: where a new file goes, what may run and who may ask, which comments earn their place. One written opinion instead of a fresh one per session, which is what keeps 547 files coherent.
Claude Code, Kimi Code and Google Gemini, chosen per job and set to review each other's work. Design ran the same way, Figma for the product thinking and generated imagery for the visual language, with me deciding what was good enough to keep.
Nothing merges on a model's confidence. Types, dead code, formatting and lint run before every commit, then a full production build. When a rule gets silenced instead of satisfied, the rule is the thing that is wrong, and it goes.
The Build
The way I worked changed shape three times. Single prompts against single files, then a loop with written specifications and review passes, then a system that runs its own work while I keep the decisions that matter.
01 · One Prompt at a Time
The Impact
A platform I specified, designed and now operate, built without an engineering team and without hand-writing the code. It is not a claim about what I could learn if someone gave me the chance. It is running, and you are reading it.
Across 547 TypeScript files and 11 subsystems, every change through the same quality gate.
Site audits, tailored applications, lead research, outreach and calendar, driven from a phone in plain language.
Image build, health-checked container swap, and a rollback that is one previous tag.
Whether you're shaping a new product or improving an existing one - I'd love to hear what you're working on.
Insert Figma Library Screenshot
Showcase the organized variants, auto-layout, and property panel.
Working screens and no architecture. Every session re-argued what the last one had settled, and nothing remembered yesterday. Fast enough to prototype with, nowhere near good enough to run.
02 · The Loop
Architecture written down, one agent per problem, a second model reviewing before anything merged. The quality gate stopped being something I remembered to run and became something a change cannot skip.
03 · The Engine
29 tools behind a plain-language chat interface, queued pipelines for audits and applications, scheduled jobs, and a deploy on every push. The machine does the reaching, and anything that leaves the building waits for a tap.