Project intelligence
Omni UI
Reusable interface system and component workshop
Give product teams a shared place to review reusable interface components, themes, states, and interactions before bringing them into an application.
Latest signal
Nov 15, 2026
Synced Nov 16, 2026
26
Commits · 365 days
25
Pull requests · 365 days
0
Issues · 365 days
0
Code reviews · 365 days
Public summary
Public summary
What it is
Omni UI is a shared interface workshop for teams building related digital products. Designers, developers, and technical leads can inspect reusable components, themes, and interaction states in Storybook before adopting them in an application.
The problem and business value
When every feature rebuilds its own buttons, forms, charts, and loading states, the product can become harder to maintain and less consistent to use. Omni UI gives the team a concrete reference for those decisions: how a component looks, which states it supports, and how it should behave.
It demonstrates a practical approach to design-system work for growing products and multi-application teams. A client engagement would start with the interface patterns that matter to that client's product.
What it does today
- Organizes source-owned interface primitives and shared design tokens.
- Offers Lux, Omni, and Console themes with palette and light/dark controls.
- Includes data tables, charts, loading sequences, hero compositions, and interactive graph surfaces.
- Documents component examples and states through Storybook stories and autodocs.
- Includes accessibility tooling and executable interaction stories.
- Provides a review-first component-update workflow; the browser does not silently install packages.
Integrations and data flow
The workshop uses React, TypeScript, and Storybook with a Vite builder. Consuming applications own their data, routing, and privacy decisions. Graph and product demonstrations use public-safe fixtures rather than reaching into private application databases.
AI or automation workflow
A local Storybook MCP integration can help supported developer tools inspect the workshop. It is a development aid, not an automatic production component generator. Developers still review additions, dependencies, and application integration.
Collaboration and security boundaries
The public landing introduces the project; the hosted workshop is protected through OmniRoids Core's signed authorization contract. Core owns identity and permissions. The workshop does not create a second user database or expose server credentials. Authenticated hosted access and preview configuration require their own verification.
What is coming next
The library grows around documented product needs, with component states and interaction evidence reviewed together. Client adoption would include an inventory of existing patterns, a focused component scope, and a migration plan for consuming screens.
Current activity and next step
The repository contains the component library, stories, interaction checks, theme system, and hosting gate. These are implementation assets, not a claim of accessibility certification or a measured delivery-speed improvement.
Discuss your product's interface system. Share the screens or recurring patterns that are becoming difficult to keep consistent.
Contribution graph
The work behind the work.
Commits, PRs, issues and reviews
51 recorded activities in the selected range.
All available activity
Monthly activity totals
| Month | Activities |
|---|---|
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 39 |
| 2026-10 | 2 |
| 2026-11 | 10 |
Recent activity
What is moving now.
- [OMNI-UI]docs(portfolio): add public workshop sales briefCommit · Nov 15, 2026↗
- [OMNI-UI]docs(portfolio): add public workshop sales briefPull request - merged · Nov 15, 2026↗
- [OMNI-UI]fix(tooling): preserve skill frontmatter in current formatterPull request - merged · Nov 14, 2026↗
- [OMNI-UI]fix(tooling): preserve skill frontmatter in current formatterCommit · Nov 14, 2026↗
- [OMNI-UI]chore(deps): update workshop libraries and security resolutionsCommit · Nov 14, 2026↗
- [OMNI-UI]chore(deps): update workshop libraries and security resolutionsPull request - merged · Nov 14, 2026↗
- [OMNI-UI]ci: signal automatic main deployments on the VPSPull request - merged · Nov 14, 2026↗
- [OMNI-UI]ci: signal automatic main deployments on the VPS (#22)Commit · Nov 14, 2026↗
- [OMNI-UI]chore: target node 26 and refresh the workshop toolchainPull request - merged · Nov 14, 2026↗
- [OMNI-UI]chore: target node 26 and refresh the workshop toolchainCommit · Nov 14, 2026↗
- [OMNI-UI] Audit Supabase efficiency boundariesPull request - merged · Oct 13, 2026↗
- [OMNI-UI]docs: audit Supabase efficiency boundariesCommit · Oct 13, 2026↗
- [OMNI-UI] Put the complete shadcn registry under PrimitivesPull request - merged · Sep 7, 2026↗
- [OMNI-UI]feat(primitives): expose the full shadcn registryCommit · Sep 7, 2026↗
- [OMNI-UI] Fix hero assets on the hosted workshop base pathPull request - merged · Sep 7, 2026↗
- [OMNI-UI]fix(hero): resolve assets on the hosted workshop base pathCommit · Sep 7, 2026↗
- [OMNI-UI] Port the real OmniRoids hero boot scenePull request - merged · Sep 7, 2026↗
- [OMNI-UI]fix(hero): port the real OmniRoids boot sceneCommit · Sep 7, 2026↗
- [OMNI-UI] Add full shadcn themes and compositionsPull request - merged · Sep 7, 2026↗
- [OMNI-UI] feat(workshop): add full shadcn themes and compositionsCommit · Sep 7, 2026↗
Published roadmap
What is shipped and what comes next
Delivered
- [done] Token-backed component workshop and theme system.
- [done] Documented component states, charts, tables, and graph surfaces.
Operationally pending
- [in-progress] Complete authenticated hosted and preview access verification.
Coming soon
- [planned] Add components against documented product needs.
Discuss the next step. Scope, account access, and readiness are agreed before implementation or rollout.