NIMOS / ENGINES / CUIFMARE

← THE BUILD SYSTEM

CUIFMARE

THE UI ENGINE

Core UI Frameworks & Registry Extensions

The registry of interface parts the studio reaches for before it draws a component by hand.

DRAWN BY THE HOUSE

One mark per engine, on one grid, in one hand.

20

TOOLS

PROJECT

WIRE

USED

THIS BUILD

3 shadcn pulls recorded: magicui grid-pattern, border-beam, blur-fade.

THE PROOF LEDGER →

WHAT

What it is

Twenty component sources, primitives and utilities: shadcn micro-registries (MagicUI, Aceternity, Cult, Origin, Kokonut, HyperUI), Ariakit, Radix Icons, Headless UI, TanStack Table and Query, clsx, tailwind-merge, Lucide and react-dropzone. The registry is the market of parts; the engine is how they get into a build.

WHY

Why it exists

Pages are won or lost on component craft. Premium sources already exist, and a hand-rolled card is usually a worse card. CUIFMARE makes the good source the first stop instead of the last.

HOW

How it runs

`engctl install cuifmare --dir <project>` wires the selected parts into the build: npm installs where a package exists, `npx shadcn add` for registry components, with undeclared dependencies surfaced rather than assumed. Every pull is recorded.

WHEN

When it runs

Any page, section or component build. Before a component is written from scratch, the registry is searched.

WHO

Who owns it

CEO owns the component bar; Research watches the registries; Build does the copy-in and theming; Data keeps the usage ledger; Ops closes one component at a time.

TOOLS

The registry

The engine manifest is the source of truth. These are its entries, including the ones that are not used on this build — the proof ledger says which is which.

@magicui/react

registry

Premium animated components designed for high-conversion landing pages.

@aceternity/ui

registry

Bold, highly-animated components — moving borders, aurora backgrounds, spotlight cards.

@hyperui/react

vendorsource ↗

Clean, accessible, raw Tailwind components for rapid layout scaffolding — copy-paste, zero dependencies.

@radix-ui/react-icons

npm

Highly optimized primitive icons that match primitive headless behaviors.

@ariakit/react

npm

Fully unstyled, highly accessible components for custom design systems.

@heroui/react

npm

Component primitives (upstream of legacy @nextui-org/react)

@saas-ui/react

npm

Advanced component library for dashboards and SaaS builds.

@kokonut/ui

vendorsource ↗

Next-gen layout blocks optimized for modern, minimalist web applications.

@origin-ui/react

registry

Advanced micro-interactions — copy-paste friendly, state-driven UI elements.

@cult-ui/react

registry

Avant-garde, brutalist, and modern kinetic components for creative landing experiences.

@tanstack/react-table

npm

Headless data organization — grids, sorting, filtering, virtualization.

@tanstack/react-query

npm

Persistent client-state caching for async data layers.

@radix-ui/react-slot

npm

asChild element-forwarding primitive for unified component APIs.

@headlessui/react

npm

Unstyled logic templates from the Tailwind engineering team.

clsx

npm

Clean conditional class-string composition.

tailwind-merge

npm

Eliminates conflicting Tailwind utility overrides in composed components.

@vanilla-extract/css

npm

Type-safe, zero-runtime CSS-in-JS.

styled-jsx

npm

Scoped, isolated style modules for component nodes (Next.js native).

lucide-react

npm

Consistently structured community vector icon set.

react-dropzone

npm

Responsive file-ingestion dropzone components.

20 registry entries. The proof ledger on the Gantry page says which of them this build actually used.

RUN

Run it

ENGCTL / THE ENGINE FLOOR

$ engctl show cuifmare$ engctl awaken cuifmare$ engctl install cuifmare --dir ./site

`engctl` is the registry control surface. `awaken` checks wiring before it activates a cell; `install` writes the parts into a project.

PROOF

On this build

3 shadcn pulls recorded: magicui grid-pattern, border-beam, blur-fade.

N/A and PARTIAL are stated, not hidden. The ledger is generated from this project, not from a template.

LIMITS

What this does not claim

The count is a registry count, not a claim that every part shipped. The proof ledger above names the pulls this build actually made.

The engine is the how. The brief is the start.

CUIFMARE — the the ui engine | Nimos