From flat frames to layered motion — shipped as a disciplined component stack.
Front-of-house craft is half hospitality,
half systems thinking — signal over noise, always.
Fragment
This build exists to show how modules snap together under scroll pressure —
not to anchor a biography. The narrative here is technical: tokens, easing,
shader budgets, and the quiet discipline of empty space.
Side projects feed the sandbox: generative type, tiny physics toys,
and experiments that never ship but sharpen judgment for the ones that do.
If you need a name on the tin, replace the current footer details
and metadata — the layout will not care.
—
Product surfaces
Ship interfaces that stay legible when marketing asks for one more hero variant.
Component APIs before pixel polish — props, slots, and failure states mapped early.
Performance is a creative constraint, not a ticket at the end.
Search & discovery
Search is navigation: facets, synonyms, and empty states deserve the same care as the hero.
Measure what people actually type, not what the brief assumed they would.
Experience design
Layout is a contract: spacing, type scale, and motion cues train people once, then get out of the way.
Research shows up as annotated frames, not a slide deck that never meets code.
Delivery arc
Slices move from sketch to staging with explicit acceptance checks — no surprise QA at the end.
The interface is treated like infrastructure: versioned, reviewed, and measured.
Team cadence
Ceremony stays light: async updates, focused reviews, and a single source of truth for decisions.
Tools change; habits stay — small diffs, loud tests, readable history.