Constructive Blocks

Use the live @constructive registry and the consumer's current project configuration as the source of truth. Never require a Blocks commit, branch, catalog snapshot, or fixed package version.

Choose the distribution

• Use the @constructive shadcn registry when the application should own and edit the installed source. Console Kit, feature packs, presets, application blocks, and registry primitives use this path.
• Use an @constructive-io/* npm package when the application wants a packaged API. The UI, data, Sheets, command-palette, and Schema Builder packages are independent of their source-installable registry surfaces.
• Do not install both distributions for the same presentation surface unless the item's live registry metadata explicitly declares a package dependency.

Read surface selection and ownership before choosing a root for an application block, feature pack, or Console Kit.