Architecture · 01
A strict, one-way dependency chain: ui → patterns → architectures. Each layer works on its own. None of them force the next.
@venator-ui/ui
UI primitives
Typed, accessible, composable React components. Import what you need, extend with className. Nothing opinionated about composition.
@venator-ui/patterns
Structural patterns
Reusable compositions that define how UI is arranged into pages. Layout scaffolds, not content. You fill them in.
@venator-ui/archetypes
Application architectures
Complete architectures deployed via CLI. Once scaffolded the code is yours — no runtime dependency, no lock-in.
Archetypes · 02
One command scaffolds a complete architecture. Sidebar navigation, header, module grid, tokens wired in. The output is yours — extend it, delete half of it, it's code, not config.
Last 30 days · updated just now
Apr 01 – Apr 17 · 2026
Weekly average · 62
Last 30 days · updated just now
Primitives · 03
Accessible, composable, typed primitives. Built with Tailwind CSS and design tokens.
Button
Badge
Input
Switch
Checkbox
Slider
Progress
Kbd · Tooltip
Tabs
Primitives are accessible by default.
Table
| Package | Version | Status |
|---|---|---|
| tokens | 0.1.2 | ready |
| ui | 0.1.3 | ready |
| patterns | 0.1.1 | beta |
| archetypes | 0.1.7 | beta |
Live · 04
Every primitive is tweakable in-browser. Props on the left, rendered component in the middle, generated JSX on the right.
Why Venator · 05
Structure is the thing that's hard to change once a project grows. Venator gets it right on day one, so you can change the rest freely.
Zero runtime weight
Tree-shakeable, no CSS-in-JS, no provider.
Fully typed
Strict TypeScript in every package.
CLI-deployed archetypes
Scaffold complete architectures in one command.
Four adoption levels
Start with a Button. Scale to a full app.
No lock-in
Archetypes are copied — the code is yours.
Accessible by default
WAI-ARIA patterns wired in from the primitive layer.