The installation flow is intentionally simple: pick a component, run the command, and keep the generated source files inside your own app. That gives your team immediate ownership over fluid motion, styling, structure, and accessibility decisions.
Registry workflow
The default path mirrors the way shadcn-style registries are meant to be used. Install a single component first, confirm the generated files look right in your project, and then repeat the same flow as your interface grows.
npx shadcn@latest add @iconiq/button- Run one command for the component you want to add.
- Let the registry place the implementation directly in your codebase.
- Review the files locally and adjust them to match your product conventions.
Registry URL
If you want to reference a specific registry file directly, you can install from the hosted JSON path instead of the scoped package name. This is useful when you want the exact source URL in front of you during review or automation.
npx shadcn@latest add https://iconiqui.com/r/button.json- The direct URL follows the same shadcn add flow as the scoped component command.
- It works well when you want to point teammates or tooling at a specific registry entry.
Sample entries
Every documented component follows the same installation pattern. Here are a few representative entries you can open right away.
Browse the full catalog from the component docs and use the same install flow whenever you want to add another piece to your interface.