A UX audit, a starting point that fills itself in, and a coded prototype that ended up being the thing decisions were made on.
Feri Horvath, Product Designer
I solve complex problems for startups and larger companies, and design visuals from pitch decks to coded landing pages.
About

Product Designer, 8+ years in design. SaaS B2B [Grafbase], DeFi [KeyFi], and crypto [SelfKey]. Started in 2014 in frontend, marketing sites in iGaming [Mr Green], then a hybrid UI design and frontend role at SelfKey. A dedicated Product Designer from KeyFi on.
Independent since January 2026, working with teams from startups to enterprise.
- Product DesignerIndependent · Product design for startups to enterprise · Remoteto now
- Product DesignerGrafbase · SaaS, GraphQL Federation platform · Remoteto
- Product DesignerKeyFi · DeFi, multi-chain portfolio and yield platform · Remoteto
- Full Stack UI DesignerSelfKey · Blockchain, digital identity · Remoteto
- Front End Web DeveloperMr Green · iGaming, online casino marketing sites · Maltato
- Front End Developer and UI DesignerStateshifter Labs · Web apps and prototyping · London, UKto
References
Closing the gap
I work on the gap between design and development, and try to bring the two closer with every project.
Across several projects, iterating in a coded prototype and handing that over, instead of a Figma file, proved more efficient, and the teams chose to keep working that way.
This is how a new feature gets built now: a prompt, the design rules and a short research, two or more directions to pick from, then the code rules and a pull request.
Once the tokens and components were in place, feedback came faster and iterations got shorter. The team could walk every path themselves, and thanks to the rule set they could try out new features while the result stayed on brand and consistent.
- In the terminal, on the branch feature-pricing-section, the prompt is typed: add a pricing section.
- The design rules are read and saved to the session memory. At the same time a research page collects real pricing pages and draws two pricing sections in the rules, each with a Free and a Pro card: one centered with smaller prices, one left aligned with a dark Pro card and an outlined button on Free.
- The left aligned direction with the dark Pro card is picked.
- The code rules run: the existing PricingCard component is reused, a hardcoded colour becomes the component token pricingCardFeaturedBackground, and lint, types, QA and the pre-commit hook pass.
- The result runs on localhost as a working prototype: the cursor hovers the Pro card and its Get started button, and pull request 42 is ready with an Open PR button.
Blog
I didn't have access to the code.
There was a project where the repo existed, but I had no access to it. No Figma file either, just a live app and a browser inspector — how I map an existing design system before building anything on top of it with AI.
Zero to production: How I design from Terminal, without Figma
Multiple projects, no Figma. A complete landing page with a design system, mobile responsiveness, and animated components — built entirely from the command line.

















