Yomi

Appearance

YomiReact repair context for AI coding agents

Move from a visible UI symptom to the source owner, runtime trace plan, and verification loop.

Get Started
See the Demo
Why Yomi

Visible symptom to source owner

Start from the label, button, input, or panel the user can see, then get a source-linked repair contract.

Repair-oriented trace planning

Use plan-trace to pick the smallest action, state, effect, cache, store, form, or render targets before editing.

Agent-readable JSON

Commands return stable JSON contracts so coding agents can chain repair, instrumentation, and verification.

Minimal Loop ​

bash
npx @isamisushi/yomi@latest index --force
npx @isamisushi/yomi@latest repair "Customer search"
npx @isamisushi/yomi@latest plan-trace "Customer search"
npx @isamisushi/yomi@latest verify browser-scenario --scenarioFile <path> --url <url>

Yomi is not a browser automation framework, React DevTools replacement, or UI generator. It is a focused layer for React repair work where the visible UI is not enough to identify the right source owner.

Current Status ​

Yomi is early. It already includes a TypeScript-aware React extractor, compact graph queries, repair briefs, opt-in runtime instrumentation adapters, verifier scenarios, and a React repair benchmark fixture.

  1. Why Yomi - understand the narrow problem Yomi solves.
  2. Demo Walkthrough - see repair, plan-trace, and verify together.
  3. Getting Started - run Yomi locally.
  4. Agent Workflow - use Yomi during real repair work.
  5. Runtime Instrumentation - add focused app traces when ordering matters.
  6. CLI Reference - inspect command contracts.
  7. Limitations - know where the current implementation is weak.