Keeping Design and Architecture in Sync
Design and development moved in parallel: the developer shaped architecture and frontend while I defined UX scope, wireframes, tokens, components, and product behavior.
Can strict architecture unlock infinite creativity?
Design System Architecture, Product Design, AI-Integrated Workflow Design
2025
Farba began as a science-lab style experiment after years of seeing themable systems blocked by technical debt and business constraints.
The goal was to prove a different model: a system that does not restrict creativity, but is still stable and low-maintenance over time.
Two breakthroughs changed the equation: OKLCH for reliable accessible palette generation, and AI-assisted implementation loops after architecture was established.
A one-color input, OKLCH palette logic, scalable tokens, and unified component states let the product effortlessly generate coherent themes without turning every new screen into a custom design task.
Prior to visual design, I translated user personas, product strategy, and complex booking flows into actionable wireframes and structural product artifacts, providing clear scope alignment for the development phase.
Once architecture and design rules were clear, AI-assisted implementation helped move from intent to working interface faster, with the developer validating quality and constraints.
Design and development moved in parallel: the developer shaped architecture and frontend while I defined UX scope, wireframes, tokens, components, and product behavior.
Some early wireframes came from AI website-builder prototypes. They were rough by design, but helped us communicate intent, test flows, expose edge cases, and align before investing in polished UI.
Figma became a live product-spec layer: notes sat beside mockups and component states to capture booking logic, schedule rules, payment details, profile behavior, and service-creation edge cases.