LumeSec Elements181 componentsshadcn registryMIT
Built in the lab.
Shipped to your repo.
Interactive components from the LumeSec design lab: controls, meters, charts and dot-matrix displays. Install one with the shadcn CLI, read every line of it, and theme it with your tokens.
React 19 // Tailwind CSS v4 // strict TypeScript // custom elements for any framework
Fig. 1 · 7 components from 3 collections, running live · click, drag, type
181 components
five collections // all live
One command
shadcn add // you own the source
TypeScript
React components // typed custom elements
Accessible
keyboard // ARIA // reduced motion
02How they move
Effects switch on for the state that matters.
Six rules came out of design reviews. They are why the motion reads as information rather than decoration.
01<effort-slider>
Plain until earned.
Every level is an ordinary slider stop. Only the last one, Ultracode, grows a pixel trail, and only once the thumb arrives there.
Ultracode slider02<ui-context-meter>
Growth has a direction.
Effects start at an origin and travel one way, with an uneven front. Compaction sweeps back the other way, so the direction itself carries meaning.
Context meter03<ui-send-button>
Bursts reach past the edge.
When a reply completes, the ring closes and sparks fly past the button's bounds on their own layer. A small sparkle inside the box would not register.
Send / stop button04<ui-odometer>
Numbers are mechanical.
Counters roll digit by digit in tabular figures, in the direction of the change, so the width never jumps and the change is legible.
Odometer stepper05<hf-stat>
Legibility beats pixels.
Numbers and words are set in a regular font. The dot field glows and reacts around the value instead of forming it, so every figure stays readable and available to assistive technology.
Stat tile06<hf-area>
The data leads.
Charts move when the data changes, not for decoration: a new range morphs out of the old curve, and the header rolls to the value under the pointer.
Area chart
Higher effort thinks longer before answering. Ultracode also lets the agent plan multi-agent workflows on its own.
03Collections
Five collections. One way of moving.
0111 components
Interaction
Micro-interactions on everyday controls: send buttons, toggles, dials, meters.
0250 components
Pixel Lab
Components that live in a pixel lattice: meters, gauges, orbs, radars, AI moments.
0330 components
Pixel UI
Form controls you can ship, each with one pixel detail.
0460 components
Pixel HD
Regular controls on a high-fidelity dot field with bloom and ordered dither.
0530 components
Location
Globes, maps and connection lines for locations, visitors, sign-ins, latency and traffic between regions.
04How it works
Install. Own. Theme.
The shadcn CLI copies the source into your project. Shared engines install once. One set of tokens decides how every component looks.
Terminal: npx shadcn@latest add @lumesec/hf-gauge. Checking registry. Resolving @lumesec/hf-gauge and 2 dependencies. Created 4 files: - lib/lumesec/pixel.ts - lib/lumesec/react.ts - components/lumesec/hf-gauge.element.ts - components/lumesec/hf-gauge.tsx Gauge docs: elements.lumesec.ai/components/pixel-hd/gauge
export interface HfGaugeProps {
/** Current value, clamped to `min`–`max`. */
value?: number;
min?: number;
max?: number;
zones?: string;
label?: string;
}
export function HfGauge(props: HfGaugeProps) {
return useLumesecElement("hf-gauge", …);
}:root { --lumesec: #6219f3; }
05Works where you do
React where it fits. Any framework where it draws.
Controls and form fields are native React components on your Tailwind theme. The canvas-heavy collections are typed custom elements: they run in React with a typed wrapper, and in plain HTML, Vue or Svelte without one.
06Recently added
New on the bench.
07From LumeSec
The products these components come from.
Elements is where the LumeSec design team publishes what it builds for SecureGrid and the AI Operating Platform.
08Questions
Before you install.
01Is LumeSec Elements free?
Yes. Every component is free under the MIT license, including for commercial products, and the source is on GitHub.
02Do I need React or Tailwind CSS?
For Interaction, Pixel UI and Location, yes: they are native React 19 components styled with Tailwind CSS v4, like shadcn/ui. Pixel Lab and Pixel HD are typed custom elements that style themselves inside a shadow root, so they also run in plain HTML, Vue, Svelte or Angular, and ship with a typed React wrapper.
03How do I install a component?
With the shadcn CLI: register the @lumesec registry once, then run npx shadcn@latest add @lumesec/<name>. The TypeScript source lands in your repository, with shared modules installed once.
04Can the components match my theme?
Yes. Every component reads your shadcn theme variables (--background, --card, --foreground, --border…) plus one set of --lumesec accent tokens, so your colours, fonts and dark mode apply to all of them.
05Do they work with server rendering?
Yes. The React components render their full markup on the server and draw their canvas layers after hydration. The custom elements do not touch the DOM when imported on the server and upgrade in the browser. Both can be imported from Next.js server components.
06Who makes LumeSec Elements?
LumeSec Technologies GmbH, the company behind SecureGrid and the AI Operating Platform. Elements is where its design team publishes the components it builds for those products.