Frontend architect
Frontend Architect
Models can draft a screen.I decide what the system will accept.That is the interface layer of a financial platform.
Typed APIs over tokens and composites. One versioned source of truth for every surface that ships.
A question comes back as layout, queries, and charts. They use the system, or they don't ship.
Charts for high-cardinality data, and a stream for model output, for people who stay in the screen.
TypeScript · React · Next.js · Node · LLM tooling
The work so far, in four numbers.
Names are withheld and every screen runs on mock data. The engineering is real.
Now
Prompt-to-dashboard for a financial platform. A question becomes a draft of charts and filters from the shared system, then an editable view anyone can publish.
Custom design system. Generated dashboards are composed from the shared primitives, so they look like every other app without extra styling.
A generator that emits a new app with structure, design system, tests, and CI already wired, so the first commit is already on the platform.
Custom design system. Every new app is wired to the design system at generation, so no team has a UI library choice left to make.
Earlier field work
Dispatch and live tracking for a fleet. One job lifecycle shared by an admin console and a driver client, with every vehicle's position on a map while the trip runs.
MUI. Dense tables, date pickers, and dialogs came ready, so the effort went into the map and the job flow.
Human-in-the-loop correction for an OCR pipeline. Low-confidence reads go to a person in the field, and the correction goes back into the record.
Material. Large touch targets and clear input states, so a misread can be fixed in seconds on site.
Notes on generated screens, the systems under them, and field clients that had to work off the radio.
October 20, 2026
The claim is that models will take over and components no longer matter. The data says something else: generated products are converging on one default look, which is a reason to spend more time reviewing interfaces, not less.
October 8, 2026
A model will happily write a second platform inside a pull request. Typed edges, a small design-system surface, and generators are what keep that speed inside the architecture you already chose.
September 29, 2026
A question can come back as charts and filters. Those have to be the same primitives the rest of the product already ships, or the model has opened a second interface.
Field apps for people with gloves on, that had to keep working when the radio dropped. That was the first stretch: heavy industry, then insurance and sales tooling.
Now it is a financial platform, close to the product. Most of that work has no public screen. It is the layer under the product: rendering, and the contracts a generated view has to keep.
I build with agents in that loop, including on this site. Ten years of the path is on LinkedIn. If this is the frontend work you need, write to me.