ndekoui

The rules for writing UI that looks and moves like ndekoui: surfaces and hairlines, radius, colour, type, how to compose the Base UI primitives, the motion signatures and their timing, and what to avoid. Call it once before writing UI. Pass section with a number or a title ("7", "motion") to read one section of the design system in full, or "all" for the whole document.

Build the shadcn CLI command that installs one or more ndekoui items, for npm, pnpm, yarn or bun. Returns the command with full registry URLs, which works in any shadcn project, and the shorter @ndeko form for projects whose components.json declares the namespace.

Get one ndekoui item by name: the full source of its files, its npm dependencies, the registry items it pulls in, the shadcn command that installs it and its page on ui.ndekocode.dev. Large templates return the source of their first files and list the rest; pass file with a path from that list to read one file.

Summarise the theme item every ndekoui piece depends on: the colour tokens with their light and dark values, the radius and easing tokens, and the utilities it adds (hairlines, chip-3d, keycap-3d, gem-plate, surface-raised, surface-brand). Read it before changing colours or writing new styles.

The map of the ndekoui catalogue with counts: primitive groups, component families and their categories, block groups, template groups, motion groups and library items. Use the slugs it returns as the category of list_items.

List ndekoui registry items of one kind. Kinds: primitive (Base UI building blocks such as button or dialog), component (ready compositions such as accordion-01), block (product sections such as heroes-01), template (whole pages), motion (animation components) and lib (theme, utilities, icons, sample images, hooks). Narrow with category: a category or group slug such as accordion, heroes or application, or a component family such as forms or overlays. Paged with offset and limit.

Search the ndekoui registry by words, ranked like the search on ui.ndekocode.dev: titles first, then names, groups and descriptions. Use it before list_items when you know what you need ("pricing", "date range", "kanban"). Filter by kind: primitive, component, block, template, motion or lib.