ABOUT · NOT A BIO PAGE · A PRACTICE PAGE
I make complex things
feel inevitable.
- BASED
- Boston, MA
- PRACTICE
- Product Design + Front-End
- FOCUS
- Systems · AI Workflows · Enterprise UX
- BUILDING FOR WEB SINCE
- 2017
- PRODUCT DESIGN FOCUSED SINCE
- 2022
01 · BIO
The short version.
I started exploring design and front-end development in 2005, during my early studies in Cape Verde, and continued through my Bachelor’s at the New England Institute of Art in Massachusetts. My professional product and UX career sharpened in 2017 at StudentUniverse, where I learned how product design behaves under real engineering and business constraints. Since then I’ve moved deeper into systems work, enterprise UX, and the human side of AI products.
Most recently I led design initiatives at Modulate, working across ToxMod, Voice Vault, internal moderation and admin tools, executive dashboards, authentication flows, and the shared design system underneath. The work was high-consequence enterprise UX: dense surfaces, cross-functional review, and the daily question of how a human should decide what to do with AI signal. I worked closely with engineering, product, QA, and trust-and-safety stakeholders — and I implemented in front-end where it shortened the loop.
I work as a product designer and front-end developer in the same pass, which means I design for what’s actually shippable, not what looks good in Figma alone. AI is a working tool in that loop — a critique partner, a scaffolding generator, a way to compress the gap between concept and code. I use it daily and pragmatically; the design decisions in the middle still happen in my head.
- 01Operational tools where AI signal becomes a human decision in under a second.
- 02Data-informed dashboards that hold up across moderator, manager, and exec roles.
- 03Compressing the design-to-code loop with Cursor, Claude, and Figma Make.
- 04Patterns for AI-assisted prototyping inside enterprise constraints, not around them.
- 05Lightening design systems without losing the structural truth they protect.
Figma · FigJam
Where the system lives. Tokens, flows, components, working canvases.
React + front-end
Where designs survive contact with reality.
Claude
Critique partner. Edge-case generator. Copy editor.
ChatGPT
Second opinion. Different blind spots than Claude.
Gemini · Google AI Studio
Multi-modal exploration. Voice and vision prototypes.
Figma Make
Generative scaffolding for new surfaces inside the system.
Lovable
Concept-to-clickable in an afternoon.
UX Pilot
Rapid IA and flow generation when the brief is still soft.
Magic Patterns
Exploring component variations at speed.
Stitch
Visual UI experimentation, throwaway-friendly.
Subframe
Design-system-aware UI generation that respects tokens.
Cursor
Where design becomes shippable code.
04 · PHILOSOPHY
How I work.
- Systems before screens. Enterprise products are components, states, density modes, and time—not a sequence of hero frames. I think in that order so reviews with product and engineering stay tied to what we actually ship.
- Front-end fluency changes the design. I implement in React. What is pragmatic to build informs the canvas alongside brand and usability—and it gives engineering and me a shared vocabulary when we negotiate tradeoffs.
- AI is a collaborator, not an author. I use AI to shorten the distance between idea and artifact, surface edge cases, and speed scaffolding. What we commit to still earns its place in critique; the model helps, it doesn’t decide.
- Data-informed, not data-led. Metrics sharpen the conversation with stakeholders—they should not substitute for it. I care about grounded arguments: users, constraints, incentives, then a deliberate call.
- Operational clarity over visual flash. I care most about outcomes for real operators: the right state at the right beat under load. Quiet UI that reads fast beats a memorable decoration that adds cognitive tax.
- Feedback is part of the work. I take critique seriously and try to give it back the same way: specific, tied to shared goals, actionable. Strong views, open to revision when we learn something new from design, eng, QA, or the field—iteration is ordinary, not a crisis.
- Collaboration is craftsmanship. Respect for engineering, product, QA, and stakeholders is not soft culture—it keeps the craft honest. I stay curious about what they see before I’ve drawn it; that gap is where assumptions die. Prepared reviews, clear async signals, patience with the messy middle, low drama. I am ambitious about what we ship; I try to leave the room calmer than I found it.