
Company website
Armazém Wazlawick
The restaurant menu was a single image and is now structured text that is easy to read on a phone.
Design happens in code too.
I'm a design engineer working on the frontend, taking care of every detail of the interface.
A bit of my story and what I like to do.
Hi, I'm Adeonir, and I like building things for the internet. As a frontend and design engineer, I explore ideas through prototypes, create functional and accessible interfaces, build component libraries and design systems. I especially enjoy working at the intersection of design and code, always with an eye for detail.
After more than a decade as a graphic designer working on advertising materials, books, and magazines, I moved into frontend development. Day to day, I work mainly with React, TypeScript, Next.js, and Tailwind, and I use AI agents like Claude Code and Codex across the whole cycle, from specs and planning to implementation and review. I work in English at a professional level and have collaborated with teams in Europe and the US.
Outside of work, I build a few personal projects where I design the interface and define the architecture, and get to practice backend and mobile development too.
In my spare time, I like spending time with family, collecting Hot Wheels with my son, watching TV shows and movies, and hanging out with friends.
A few projects I helped build over the last years.

Company website
The restaurant menu was a single image and is now structured text that is easy to read on a phone.

Anniversary site
Celebrates my parents' 50th wedding anniversary, with a photo gallery, a timeline, and a guestbook for family and friends.

Company website
A travel agency that moved from a traditional WordPress theme to a headless architecture with pre-rendered pages.
Day to day, I work with teams to build interfaces.
Artificial intelligence
I use AI agents to plan solutions, create prototypes, and test code. I also integrate AI features into products, like the audio narration on this site.
Design systems
I keep the component library organized and documented, so the team can build new screens to the same standard without rewriting what's already there.
Accessible interfaces
I work on accessibility from the first component, so the interface also works with keyboard navigation or a screen reader.
Performance
I care about how each screen performs, especially how long it takes to load and how it responds to interactions.
It can be about development, a project, or just to say hi.