Introduction

cano is not a component package. There is nothing to npm install and no version to track. Instead, the CLI copies real, readable component source into your codebase, where it becomes yours to edit, extend, or delete. shadcn/ui gives you correct, neutral primitives; cano is the design layer on top — 68 opinionated, production-grade components covering the states most kits skip: loading, empty, error, and full keyboard support.

Quick start

Already using shadcn/ui? Add any component in one command — its dependencies, including shadcn primitives, are resolved automatically.

Starting fresh, or want a guided experience? See Installation, or jump straight to the new Cano CLI — a full-screen terminal app that installs, browses, and scaffolds for you.

How it fits shadcn

cano is built on shadcn, not a competitor to it. Components drop into an existing shadcn project without conflicts: the same components.json, the same cn() utility, and the same CSS variable names.

Principles

• You own the code. Source lands in your project at components/ui/. No dependency to outgrow.
• Designed, not assembled. Every component is accessible and production-grade out of the box.
• Free, forever. MIT-licensed — the CLI, the registry, the components, and the docs.

Next steps

• Installation — set up a project from scratch.
• Using components — add, update, and own your components.
• Cano CLI — the interactive terminal app.
• Browse all 68 components.