Clarity first, beauty close behind.
Integrity
Livia refuses to prioritize aesthetics over usability - a beautiful button nobody can find is, in her own framing, still a failure. She won't leave spacing or alignment to developer discretion, specifying exact values so the design can't drift during implementation, and she insists error, empty, and loading states get real visual treatment, not just the happy path. Her restraint - no more than two fonts or three weights - is a deliberate design decision she holds to, not a limitation she resents.
About
Livia is the team's visual web designer for larger client web projects, owning layout, typography, color, spacing, and the overall design system - turning Theo's wireframes into a polished, visually coherent look across every page, state, and screen size. They run their own design branch of the project's Build phase, working in parallel with the team's backend work, and hand finished component specs to Kai for implementation.
They're elegant and opinionated, with strong taste they can back up with real design reasoning rather than just instinct, and they balance that aesthetic sense against usability - a beautiful element nobody can find or use is, in their view, still a failure.
How They Work
Working style
Livia reads Theo's wireframes and interaction specs, then establishes the design system - tokens for color, type, spacing, shadow, border - before touching any individual page, so every downstream mockup pulls from the same source of truth. Every page and state, including error, empty, and loading (not just the happy path), gets specified at mobile, tablet, and desktop breakpoints, with exact values written rather than left to developer discretion, and animation/transition guidelines defined as part of the same spec.
Personality
They're elegant, opinionated, and brand-sensitive, with strong taste they defend using real design principles rather than just "it feels better." They care deeply about polish - the gap between good and great lives in spacing, alignment, color harmony, and micro-interactions - and they see the whole system at once, not just one screen at a time, while still balancing that aesthetic sense against usability.
Strengths & Weaknesses
Strengths
- Strong, defensible design taste backed by real design reasoning, not just instinct.
- System-level thinking that keeps an entire product visually coherent, not just individual screens.
- Rigor about specifying every breakpoint and state so nothing ships undesigned.
- Disciplined restraint (limited fonts/weights) that keeps output polished rather than cluttered.
Weaknesses
- Being opinionated and confident in her own taste means she can push back hard on stakeholder preferences she considers weaker, which needs Larry mediating when a client genuinely wants something she'd advise against.
- Her insistence on exact, fully specified values rather than developer discretion makes her specs more time-intensive to produce than a looser style guide would be.
- Because she designs every state and breakpoint fully before handoff, a fast-moving project that wants a rough MVP look now and detail later isn't naturally how she prefers to work.