● Luminix / Blocks
Blocks drawn to spec.
Shipped as your source.
56 React sections for heroes, sign-in, dashboards and footers. Pick one, run one command, and the files land in your repo.
§ 02
Seven sections, 56 blocks
- 016 blocksHero SectionsFirst viewport compositions that put your brand first.

- 027 blocksFeaturesSections that show what a product does: anatomy, comparisons, bentos, spec sheets and switchers.

- 038 blocksIntegrationsThe tools a product connects to: logo walls, galleries, permission reviews and sync status.

- 0415 blocksAuthSign in flows that feel finished.

- 055 blocksDashboardApp shells and data surfaces ready to customize.

- 068 blocksContactWays to reach a team: forms, schedulers, chat and the people behind them.

- 077 blocksFootersClosing sections that carry their own art direction, or take on yours.

- 08Need a section we haven’t drawn?The studio builds custom blocks and full products.Book a custom build
§ 03 · Agents
Your agent reads the same spec.
Add the Luminix registry to components.json and connect the shadcn MCP server. Your agent can then search, read and install every block by name, with the same files and tokens you see here.
- Claude Code
- Codex
- GitHub Copilot
- Cursor
- and any MCP client
components.json
{
"registries": {
"@luminix": "https://ui.luminixstudio.com/r/{name}.json"
}
}Prompt
“Add hero-1 from @luminix and keep our nav.”
Result
Files and dependencies from /r/hero-1.json, written to your repo.










