AI Product Builder & Design Engineer
Where architecture meets code.
Łódź · remote · open to full-time roles and freelance
Selected Works 2026
Beyond the
code.
Philosophy
I'm an architect who moved from designing buildings to designing products. The degree wasn't a detour — spatial thinking, composition, and the habit of understanding a problem before drawing the first line are exactly what interface work demands.
Today I build complete digital products: interface design, production frontend, and the AI workflow underneath. Working end to end means nothing gets lost in handoff — the person who decided the layout is the same person who shipped it.
What I care about is the part most projects skip: making something that's actually finished. Fast, considered, working as well on a three-year-old phone as on a studio display. Hungry for knowledge, concrete in execution, still looking for solutions nobody has tried yet.
How I Work
AI isn't a shortcut in my process — it's a team I direct. Every project here went from research to production through this pipeline.
Research
Before anything gets designed, I dig into the problem: how the field works, what competitors got right, where existing products frustrate people. I collect references and interface patterns until I understand what the project actually has to solve.
Concept & Direction
With the research in hand, I work through visual direction and interface concepts in Claude Design — layout, hierarchy, type, color. This is where the project gets its character, and where most of the throwaway ideas happen.
Structure & Content
Cowork is where the project gets its skeleton: information architecture, copy — in two languages where the project calls for it — image processing and asset prep. Nothing reaches the build stage half-finished.
Build
Production code with Claude Code as a development partner — React, Next.js, TypeScript. I direct the architecture and review every change; the AI handles the volume, not the decisions.
Refinement
This is where the work moves from broad strokes to detail: spacing, type scale, contrast, the states nobody notices until they're wrong. Motion belongs here too, wherever it earns its place — a transition or a hover that makes an interface feel finished rather than decorated.
Ship
Deployed on Vercel, then tested on real devices — because the bugs that matter rarely show up in a desktop browser. Iterate, refine, repeat.
Architect's Eye
SpaceSpatial hierarchy → InformationInformation hierarchy
Moving someone through a building and moving them through an interface is the same discipline: deciding what they notice first, what waits until they need it, and how they always know where they are. Five years of designing space turned out to be five years of designing user flows.
CompositionComposition → LayoutLayout
Architectural boards taught me to compose — balance, light and proportion, knowing when a layout is crowded before anyone can explain why. That instinct transfers directly to a screen, and it's the part of design that's hardest to learn from tutorials.
DetailConstruction detail → InteractionsMicrointeractions
In architecture, quality lives in the detail — the joint nobody notices when it's right. Interfaces work the same way: the transition, the hover state, the loading skeleton. Users won't name them, but they feel the difference.
Core Stack
Frontend
- React / Next.js
- TypeScript
- Tailwind CSS
- Framer Motion
Backend & Deploy
- Vercel
- Git / GitHub
AI Workflow
- Claude Code
- Claude Design
- Cowork
- Gemini
Design
- Figma
Projects built
Tools & technologies
Curiosity & drive