ns-ui

<!-- generated:count start -->228<!-- generated:count end --> React components you install by URL, no package to depend on. Every one is

built around a single interaction and gated by a Playwright suite that refuses to pass a component whose hover looks identical to its resting state.

Two collections. core (<!-- generated:core start -->188<!-- generated:core end -->) is restrained and production-facing, Geist-dark. loud (<!-- generated:loud start -->40<!-- generated:loud end -->) is a deliberately flashy showcase.

Browse them live at design.helpmarq.com.

hero-particles-webgl — a field that answers the cursor	hero-isobar-contours — contour lines that bunch toward the CTA
gallery-coverflow-caustic — drag to scrub, flick for momentum	picker-pareto-frontier — pick a point on a pareto frontier
compare-crack-seam — the before/after divider is a fracture	not-found-knockout — type carved out of the surface

Install

Any shadcn-configured project, zero config:

npx shadcn add https://design.helpmarq.com/r/<name>.json

That drops the source at components/ui/<name>.tsx and installs the component's npm dependencies. There is no ns-ui package and nothing to keep in sync. The code is yours to edit.

New project:

npx shadcn init -d
npx shadcn add https://design.helpmarq.com/r/gallery-coverflow-caustic.json

For agents

GET https://design.helpmarq.com/llms.txt

One fetch returns the whole catalog as plain text: every component, its props, the situation it suits, and its exact install command. No tool definitions, no pagination. An agent that can make an HTTP request can pick the right component and install it in two steps.

llms-full.txt at the same origin adds the full behavioral description per component, hand-written rather than derived from tags, for the cases where several components share a UI role and a model has to tell them apart.

/registry.json serves the standard shadcn registry index for tools that expect it.

Prefer tools over a one-time fetch (an agent working across a whole session, not just picking one component up front)? mcp/ is an MCP server over the same catalog — search_components, get_component (full prop signature + real source), list_categories, install_command, and get_conventions (the token/theming contract). npx -y @nikolas.sapa/ns-ui-mcp, stdio transport, per-client config at design.helpmarq.com/connect or mcp/README.md.

There's also a thin CLI, cli/ (@nikolas.sapa/ns-ui): npx @nikolas.sapa/ns-ui add <name> installs a component, `sea