open-ux.dev
AI agents build UI quickly, but they can't defend their design choices. Open UX gives them sourced UX rules, so every decision comes with a reason.
Stop agents from inventing UX rules: open-ux.dev case studyyonatan lev ari / ux, ui and design infra lead
Twenty years in UX/UI and product taught me to look for the patterns underneath. Today those patterns shape design systems, product rules and AI workflows that teams and agents build on.
Building design systems with teams
Tokens, components and the shared language around them.
Writing UX specs people actually read
Specs that walk stakeholders and devs to the same answer.
Helping product owners think UX and dev
Teaching owners to see flows, states and edge cases.
Bringing UX craft into AI workflows
Rules and checks that help agents design with reasons, not guesses.
AI agents build UI quickly, but they can't defend their design choices. Open UX gives them sourced UX rules, so every decision comes with a reason.
Stop agents from inventing UX rules: open-ux.dev case studyContext and memory don't always carry from one agent session to the next. Orchestra keeps shared memory and skills in one place, so the work builds on itself.
See the agents' cloud brain: Orchestra case studyA rapid-logging journal for iPhone, with boards that turn everyday life workflows into simple routines.
See why I built Kee: Kee case studyNew faces, new work, something to learn. I'm always open to sharing my ideas and experience in the following paths.
New tools often bring a new process nobody asked for. Here, AI slots into the process you already have. The steps that work stay, and your team ships faster.
You get a clear map of where AI helps your flow, and where it should stay out.
Plan AI into my design workflow: Design Workflows with AI ConsultationProducts drift when each stage sets its own bar. I stay from discovery to handoff, so the product keeps one standard. Scope comes first, and ready and done mean the same thing to everyone.
You get one shared idea of ready and done, from the first sketch to handoff.
Review my product from discovery to handoff: Product Life Cycle ConsultationDesign and code drift apart when the docs come last. Here the docs come first. Every change lands there, then reaches the product.
You get docs your team trusts, and a product that matches them.
Start a design system review: Design System Consultation