My entry into a project doesn't start with the interface, but with understanding: How does the system work? Who uses it, when, why, and what gets in their way? Only then comes structure, then design.

What sets me apart from many designers: I speak the language of developers fluently. Deep CSS knowledge, an understanding of frontend architecture, and the experience of translating design tokens directly into code structures. This turns handoffs into conversations, not hand-overs.

I'm also there where documentation and structure are needed: breaking down complex systems, translating them into clear logic, and enabling teams to work well independently.