Source-owned UI
Components that leave the nest with you.
Describe what you need, copy the source, and own every line in your tree.
npx @jabkit/cli add hero307- 214components
- 82atoms
- 113marketing blocks
- 19dashboard blocks
- 111with no extra deps
- 6MCP tools
- 2themes, one source
- 1command to install
- 0lock-in
A short path from idea to code.
The catalogue is a working interface for people and agents, not a gallery that ends at the browser.
01 · DescribeSay what you need
Search by intent, tag, or category. Metadata makes a component findable before you know its name.
02 · AddCopy it into your tree
One CLI command drops source files into your project. Dependencies resolve with the install plan.
03 · OwnShape it for your product
The files are yours. Edit tokens, props, and markup without fighting a locked package.
Today's menu
Start with something real.
Pick a shelf. Each one opens live previews, source, stories, and install plans.
- Heroes20 components
- Pricing4 components
- Case studies2 components
- Compare1 component
- Code examples2 components


the card catalogue
Findable by intent.
Tags are part of the contract. Filter the catalogue before you know a component name.

wired for robots
Built for agent handoff.
MCP tools expose search, install plans, and conventions so an agent can resolve a component the same way a human would.
- 01
get_conventionsanswer two discovery questions
- 02
search_componentscompare intent and brand fit
- 03
get_install_planplan the selected components
curl -X POST https://jabkit.joseadrianbuctuanon.dev/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_components","arguments":{"query":"hero"}}}'Light and dark
Both themes, one source.
Every component ships with both palettes from the same tokens.



curtain call
Own the files. Ship the interface.
Browse the catalogue, copy a component, and keep building without a locked dependency.
$ npx @jabkit/cli init