cli: Configure and use multiple resource registries with namespace support.

[akshay2604]

Which scope/s are relevant/related to the feature request?

Don't know / other

Information

Description
Shadcn provides a way to add custom components that you or your team have created directly into your codebase via a registry system.
👉 Shadcn Registry Documentation

Why We Need This in Spartan
One of Shadcn’s biggest strengths is that it enables developers to build their own design system on top of it. It provides a beautiful set of defaults and a clear framework for extension — a solid foundation rather than a rigid end product.

This flexibility is exactly what developers are looking for when choosing something like Spartan. We don’t want to be locked into a fixed design system, but we also don’t want to reinvent every component from scratch. Spartan’s minimal, composable philosophy already makes it a great candidate to serve as the base layer for custom design systems.

However, Spartan currently lacks the ability and tooling to easily enable teams to extend it or maintain their own registries of components. Supporting multiple registries with namespace support would allow teams to 1. define and publish their own components and design tokens. 2) Seamlessly integrate internal registries alongside Spartan’s core registry. 3) Build and evolve their own design systems on top of Spartan, not beside it.
\

Describe any alternatives/workarounds you're currently using

No response

I would be willing to submit a PR to fix this issue

• Yes
• No