Orchestero Elements
Orchestero's shadcn-compatible directory registry for product interfaces, AI chat experiences, and reusable design system primitives, with a style catalog that starts with macOS and expands into Pixel, macOS, and future Orchestero looks, served from elements.orchestero.com.
# macOS style is coming soonThe current Orchestero baseline: crisp shadcn-compatible primitives, AI chat pieces, and production-ready registry items.
A sharper, grid-forward treatment planned for playful builders, creative tools, and retro-inspired AI interfaces.
A desktop-native direction planned for calm, high-density AI workspaces and command surfaces.
Orchestero UI primitives plus AI chat components.
This style route documents the planned design direction.
Default ships today; Pixel and macOS are planned next.
Choose a style route, then install the same component names.
Orchestero uses shadcn's style-aware registry pattern so each future visual system can keep the same namespace and item names while resolving through {style}.
Best for SaaS dashboards, AI products, admin tools, and teams that want the most stable Orchestero component surface today.
Best for expressive products that still need installable, shadcn-shaped components instead of one-off visual experiments.
Best for apps that should feel familiar on desktop while keeping the same registry names and install workflow.
Built for the shadcn directory shape.
The public surface is intentionally simple: one Orchestero namespace, style-scoped JSON files, schema-validated registry items, and direct install commands for consuming apps.
AI chat components live as a first-class group.
components/chat installs Orchestero's thread, message, composer, and tool call primitives together, while still letting projects pull each piece independently.
{
"categories": ["ai", "chat"],
"meta": { "group": "chat" }
}The Orchestero component surface, grouped for scanning.
Components are owned and maintained in this repository, installable one at a time, and organized by how builders reach for them in Orchestero products.
Prepared for shadcn directory publishing when you are ready.
The public entry points are already shaped for the directory: open source, namespace-based, style-aware, and ready to validate before an upstream submission.
{
"name": "@orchestero",
"homepage": "https://elements.orchestero.com",
"url": "https://elements.orchestero.com/r/styles/{style}/{name}.json"
}