Avarlo.

Design sets the direction. Every build starts there.

Avarlo carries approved product patterns into Claude Code, Codex, and pull requests—so designers shape the system and frontend teams build from it.

Request early accessSee how it works

One decision, carried through every build.

Avarlo maps the patterns in your repo, records the direction design chooses, and makes it available wherever your team builds and reviews.

3 patterns foundcombobox
Native select
12
Custom combobox
8
Searchable menu
3
One job. Three interaction patterns.
01 · Find

Map the patterns.

See which UI patterns exist, where they appear, and where they diverge.

Approved decisionCustom combobox
Maya ChenProduct designer
Jordan LeeDesign engineer
Priya ShahProduct manager
No ownerLeave this project unassigned
Approved by HBProduct designer · Today
Approved
02 · Decide

Set the direction.

A designer chooses the intended pattern, behavior, and meaningful exceptions.

Build guidanceClaude Code · Codex
Before building this field:
Use CustomCombobox from the product UI
Use it for searchable lists with 8 or more options
For people, show avatar, name, and role
Support typing, arrow keys, Enter, and Escape
Ready to build
03 · Guide

Guide the build.

Give Claude Code and Codex the approved pattern before they write the UI.

Pull request #418
Add project owner picker1 design suggestion
components/project-owner.tsx

Use the approved CustomCombobox. This one-off menu is missing keyboard navigation and role labels.

Apply approved pattern
Avarlo automates the known and surfaces the new.
04 · Review

Carry it through review.

When a pull request diverges, surface one focused suggestion grounded in the approved decision.

I moved design into code. Then the team started building too.

I moved more of my design work from Figma into a React prototype repo. With coding agents, I could explore real interactions and product patterns instead of handing off static screens. The work moved faster.

Soon PMs and engineers were building product UI directly. Shipping accelerated, but the intent behind existing patterns did not travel with the code. Design direction needed to scale with the work.

Design needed a way to lead beyond individual screens.

The codebase remembered patterns. It did not remember intent.

I started turning repeated review comments into rules. That exposed a boundary: frequency can reveal a pattern, but it cannot choose the direction. Some decisions can be automated. Others still need human taste.

Frequency is evidence. Direction is a decision.

That boundary became Avarlo.

Designers choose the intended pattern, behavior, and meaningful exceptions. Avarlo records that decision with its source, then carries it into coding agents and pull requests as the product evolves.

Human taste decides. The system remembers.

Designers can shape the system instead of redrawing every screen. Frontend teams build from trusted direction, and the product stays coherent as more people contribute.

Hyunghwan Byun

Founder & designer