Feels right to the people using it. Obvious to the agents building it.

For agents

Agents read the types

An agent that learned on shadcn/ui writes what it knows. Ouro HX answers where the agent already looks: the type check, the source it just installed, and the console. Every message here is real output from the code, checked against the code on every CI run.

1. The agent writes

   shadcn's destructive variant

   <Button variant="destructive">Delete</Button>

   The type check

   error TS2322: Type '"destructive"' is not assignable to type '"solid" | "soft" | "outline" | "plain" | (string & { 'From shadcn? Use tone="destructive" or tone="secondary". default is "solid"; ghost and link are "plain"': never; }) | undefined'.

   The installed source components/ouro/button/button.tsx

   /** Visual weight: `solid` for the primary action, `soft` for secondary actions, `outline` for a quiet bordered control, `plain` for a borderless one. shadcn's `default` is `solid` (the default), `ghost` and `link` are `plain`, and `destructive` and `secondary` are tones: `tone="destructive"`. Any other string is a type error whose message names the fix. Variant is visual only. For a toggle, pass `aria-pressed`; for the current nav item, `aria-current="page"`. */variant?:
       | "solid"
       | "soft"
       | "outline"
       | "plain"
       | (string & { 'From shadcn? Use tone="destructive" or tone="secondary". default is "solid"; ghost and link are "plain"': never })
       | undefined;

   The console, in development

   [ouro-ui] Button: variant="destructive" is not a variant. Fix: <Button tone="destructive">.

2. The agent writes

   A loading flag named the usual way

   <Button isLoading>Save</Button>

   The type check

   error TS2322: Type 'boolean' is not assignable to type '{ 'Use <Button loading>': never; }'.

   The installed source components/ouro/button/button.tsx

   /** Not a prop. Ouro UI uses `loading`: `<Button loading>`. */isLoading?: { 'Use <Button loading>': never };

   The console, in development

   [ouro-ui] Button: isLoading is not a prop. Fix: <Button loading>.

3. The agent writes

   Radix's asChild for a link

   <Button asChild>
     <a href="/recipes">Recipes</a>
   </Button>

   The type check

   error TS2322: Type 'boolean' is not assignable to type '{ 'Use <Button href="/path">': never; }'.

   The installed source components/ouro/button/button.tsx

   /** Not a prop. To render a link, pass `href`: `<Button href="/recipes">`. For other elements, use parts. */asChild?: { 'Use <Button href="/path">': never };

   The console, in development

   [ouro-ui] Button: asChild is not a prop. Fix: <Button href="/path">.

Rules an agent doesn't have to learn

1. 01

   Props first

   A component takes props that describe the whole thing, and building-block parts wait in a separate file for when props can't say what you need.

2. 02

   Required means required

   What a component needs, like a sheet's title, is a required prop, so leaving it out is a type error.

3. 03

   One state, one prop

   loading handles the spinner, aria-busy, the screen reader announcement and the layout, so nothing else needs setting.

4. 04

   Named appearance

   tone values are the theme's token names (primary reads --primary), and variant and size are named options, so the props speak the theme's language instead of color names.

5. 05

   className is for layout

   Margins and widths go in className, and an appearance class gets a one-time warning that names the prop to use.

6. 06

   The guessed prop exists

   When an agent guesses a common name, it either works or fails the type check with an error that names the real prop, and hovering it in the editor shows the same note.

Ouro AX

Obvious to the agents using it, too

A standard of checkable claims, a kit that meets them and an X-ray that checks any command line, HTTP API or MCP server against them.

Here is one moment, seen from both sides: what you see, and what your agent sees.

notes post abc123 "Running late, start without me"notes: post: other people will see this as the person's, so it needs --why: who asked you, and what they said. Fix: notes post abc123 "Running late, start without me" --why "<who asked you, and what they said>".notes post abc123 "Running late, start without me" --why "Jo Park asked: tell Design sync I'm running late"Posted to "Design sync". Everyone in it can see it.Checked: read the room's last message back.Receipt: m1Next: notes watch abc123  (wait for a reply)

The agent's first try is refused in one line that names the fix, and nothing reaches the room until it says who asked.

Written from where agents went wrong

• 0 of 12

  Rules written from principles alone matched none of the 12 wrong turns real agents made.

• 5 → 10from 5 to 10

  Two rules written from those wrong turns took the same agent from 5 of 10 runs to 10 of 10.

• 1 → 2from 1 to 2

  A wait on the conversation the agent already knew took “tell me when someone replies” from 1 of 2 runs to 2 of 2, in about half the calls.