opt-ui
Foundation layer
Shared UI component library structured as Core → Shells → Surfaces
The page shows the surface first, then carries it into packages, harness contracts, and Builder verification.
Start BuilderAccessible parts, product frames, state contracts, and agent checks are tied into one screen-building flow. The result is not just pretty components, but product UI that can be operated.
reopt provides production-grade component modules and tools as one system: UI, data grids, editors, chat, CLI, and verification flows for building polished product interfaces with professional quality standards.
Explore modules and toolsimport { DataTable, Dialog, Toast } from "@reopt-ai/opt-ui";
import { DataGrid } from "@reopt-ai/opt-datagrid";export default defineReopt({
modules: ["ui", "datagrid", "editor", "chat"],
checks: ["a11y", "states"]
});Drag boards, remote data grids, editor drafts, and approval states sit on the same UI contract instead of becoming one-off screens.
Learn harness contractsRemote metrics and filter state are pinned to a screen contract.
DataGrid editing and save failure states are checked together.
Permissions, density, and empty state are audited per route.
The same screen result is checked in the real Builder canvas.
AI edits are compared against the active contract.
Tab order and focus rings are reviewed beside docs examples.
Changed packages and screen impact connect to release notes.
Loading, empty, error, and review states all passed.
Docs, examples, and live routes use the same metadata.
Mouse, touch, keyboard, and screen reader flows stay under the same component contract instead of being styled as separate afterthoughts.
Learn keyboard patternsTab order, shortcuts, typeahead, and focus restore follow the same rules across product screens.
Hover, resize, context menus, and drag feedback support dense desktop workflows.
Loading, empty, error, and review states are checked on real surfaces, not just component demos.
Focus returns naturally after overlays, list deletion, and drawer transitions.
Accessibility is part of the screen contract. Docs demos, Builder previews, and live routes keep the same semantic baseline.
Learn accessibilityButtons, tables, menus, and dialogs follow WAI-ARIA roles and keyboard behavior.
Touch targets, drawers, and dismiss flows hold together on small screens.
The same state matrix is repeatedly verified in docs and product routes.
Locale, density, width, and motion preferences keep changing in real products. reopt keeps those settings near authoring and verification.
View recipesSee each package's install command, docs entry point, and owned area in one place, then start with the role you need.
Open docs hubFoundation layer
Shared UI component library structured as Core → Shells → Surfaces
Data display specialist layer
Keyboard-first editable data grid — virtualization, cell editing, and remote data sync
Content editing specialist layer
AI-first content editor — dual mode with visual WYSIWYG and an NDJSON StreamCompiler
AI conversation interface layer
Streaming AI chat interface built on the Vercel AI SDK — conversations, input, and 28 renderers
v1.8.2 · 2026-06-22