Avarlo.

Let everyone build. Keep the product consistent.

Connect your React repo on GitHub. Avarlo carries your design team’s approved decisions into Claude Code and Codex, then checks every pull request against them.

Request early accessSee how it works

One decision, carried through the work.

See how one approved decision reaches coding agents before they build and each pull request before review.

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

Find the conflict.

Scan a React repo for competing patterns and the screens using them.

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

Approve the direction.

Choose the pattern, behavior, and real exceptions that carry forward.

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.

Send the approved decision to Claude Code and Codex before work begins.

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

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

View approved decision
Only designer-approved decisions become pull-request checks.
04 · Review

Check the pull request.

Check approved decisions in each pull request. New judgment still returns to design.

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.

PMs and engineers began contributing to the product directly, and shipping accelerated. But design inconsistencies multiplied with the output. I could not review every change—and if I tried, I would become the bottleneck.

More builders should not create more design cleanup.

The codebase remembered patterns. It did not remember why.

I tried turning repeated review comments into rules. That exposed a boundary: code can show what is common, but common is not always correct. Some checks can be exact. Others are arguments that still need a person.

Frequency is evidence. Direction is a decision.

That boundary became Avarlo.

A designer approves the pattern, behavior, and real exceptions that should carry forward. Avarlo keeps the source and version with that decision, gives it to Claude Code and Codex before new work begins, and checks it in every pull request.

Design sets the direction once. Avarlo carries it into every build.

That is why I am building Avarlo: so more people can ship, while design keeps shaping the product instead of reviewing every screen.

Hyunghwan Byun

Founder & designer