Worldbuilding before decoration
I prefer design systems with a point of view: type, icon rhythm, layout rules, and motion all pulling in the same direction.
Design
Built to feel drawn, not templated.
I like bold shapes, intentional type, and interfaces that still feel human once the novelty wears off. The work sits somewhere between product thinking, motion, and art direction.
Interfaces with edges
Buttons, cards, and labels should feel authored. I’m not interested in another flattened component library with no personality.
Animation that explains
Movement should reinforce state, hierarchy, and mood. If it only exists to look clever, it usually gets cut.
Type-led composition
Sometimes the answer is just better pacing, bolder contrast, and enough space for the work to breathe.
Systems that still leave room to play
I want reusable design language, not handcuffs. The system should make the weird bits easier, not flatten them out.
Development
Code that earns its keep.
I care about frontends that stay fast after the fifth feature request, systems that make change cheaper, and implementation that holds up once real content and awkward edge cases arrive.
Reusable without becoming generic
Component work should speed a team up without sanding every page into the same rectangle.
Ship the fun, keep the frame rate
I like expressive interfaces, but I’m ruthless about cutting expensive layers, wasteful animation, and interaction code that only works on a good laptop.
Make editing sane
Good implementation includes the people updating the site later. Flexible fields, clear constraints, and fewer ways to break the layout.
APIs, dashboards, and internal glue
Not every useful project is glamorous. A lot of value comes from making messy systems feel coherent and reliable.
Interactions should explain themselves
If a pattern needs a paragraph of onboarding, the design or the implementation probably needs another pass.
CV
A working CV, not a dead PDF.
Design-led frontend, product thinking, implementation, motion, CMS builds, and enough range to move from concept to shipped work without losing the thread.
Snapshot
Frontend and visual designer with a bias toward expressive interfaces, maintainable builds, and work that doesn’t collapse under production constraints.
Designing, building, and refining digital work.
The overlap where the work actually lands.
Senior creative / frontend workRecent
Led interface direction, motion details, and implementation for projects that needed both visual character and practical delivery.
Product and CMS buildsOngoing
Built maintainable sites and interaction systems with real editorial needs, not just static showcase pages.
Brand and presentation systemsCross-discipline
Worked across decks, launch materials, UI language, and supporting visuals so the output feels like one world, not disconnected files.
Skill bars
Frontend craft92%
Design direction88%
Motion / interaction84%
CMS / delivery86%
Useful in the messy bit
Rapid prototyping, stakeholder-facing polish, accessibility clean-up, performance trimming, and making a strong visual idea survive production reality.
Speaking & Writing
Posts, talks, and sharp opinions.
Writing is where I usually unpack process, systems, interface decisions, and the friction between good taste and practical delivery.
Designing systems that still feel authored
How to build reusable patterns without turning every page into the same neutral grid with different headlines.
Performance is part of the art direction
Expressive interfaces only work if they still feel good on real hardware.
From visual idea to shipped thing
Where prototypes get simplified, and where they absolutely shouldn’t.
Why bland design systems fail
A system should create coherence, not erase all the character from the work.
The useful kind of polish
Small interaction and layout decisions that make work feel deliberate instead of default.
