Start building with shadcn.
A todo list starts with a project, a theme and a few installed components. Their code lives in your repository.
Connect your components, design rules and coding agent.
Build with shared context. Refine visually. Keep it consistent.
npx canon-ds@latest setupConnect the shadcn/ui code you have, or start a new app.
npx canon-ds@latest setupChoose your agent and install for one project or all of them.
Use the Canon skill to connect this shadcn/ui project. Preserve its components and theme. Do not rebuild the app.Open your project folder. Canon inventories your library and gives your agent its design context.
Use the Canon skill to build a local todo app in a new folder, with shadcn/ui.Your agent creates the app, connects Canon and builds with the installed components.
Use your agent for product changes and Studio for shared styles. Your components and theme stay in your project.
components/ui/Button · Input · Cardglobals.cssYour themecomponents.jsonshadcn/uiAGENTS.mdInstructionsDESIGN.compact.mdDesign contextCanon MCPAgent toolsStudioVisual editingStart with shadcn. Give your agent context through Canon. Build pages with the components and theme already in your project.
A todo list starts with a project, a theme and a few installed components. Their code lives in your repository.
Through MCP, the agent asks for design rules and component details. Canon returns the imports, variants and context from your project.
Canon maps your installed library. The agent imports its Button, Input and Checkbox to build the todo list, keeping your theme and variants.
No. Your agent still builds the application. Canon gives it project design context, tools and supported style checks.
No. In library mode, Canon reads and edits the installed library. The current adapter supports shadcn/ui. Support for more libraries is planned; those adapters are not available yet. Canon does not install the entire upstream catalog or replace your components with a second visual copy.
It adds Canon to devDependencies. Canon runs during development. Your deployed application uses its own saved component source and theme CSS.
No. Instructions guide the agent, and checks detect supported violations. They are not a security boundary or a substitute for application tests, accessibility checks and visual review.