Getting started
Use with AI
llms.txt#
An index for language models: what NeonKit is, how to install it, and a link to every component. Give it to your agent as context.
Every component page also has a markdown version. Add .md to the URL, for example /components/button.md, or use the Copy page button at the top of it.
Namespaced registry#
Register NeonKit once in components.json. After that, you and your agent can refer to components by short names.
{
"registries": {
"@neonkit": "https://get-neonkit.vercel.app/r/{name}.json"
}
}npx shadcn@latest add @neonkit/switch @neonkit/dialogMCP server#
The shadcn MCP server lets agents browse, search and install from any registry in your components.json, NeonKit included.
Add the namespace above
The MCP server reads registries from your project config.
Connect your client
npx shadcn@latest mcp init --client cursorSwap
cursorforvscode,codexor whichever MCP client you use.Ask
- Show me the components in the neonkit registry.
- Add the NeonKit switch and slider to the settings page and color them lime.
- Build a sign-in card with NeonKit input, checkbox and button, magenta accent.
Tell your agent to use it#
Add this to AGENTS.md or your editor's rules file, and new UI will reach for NeonKit by default.
## UI components
Use NeonKit for UI: https://get-neonkit.vercel.app/llms.txt
- Install with `npx shadcn@latest add @neonkit/<name>`
- Color with the `color` prop (palette name or hex), or wrap a section in style={neonVars("<color>")}
- Dark backgrounds only, around #05060aCopy-paste prompt#
For tools without MCP, paste this at the start of a chat.
Read https://get-neonkit.vercel.app/llms.txt. Use NeonKit components for the UI in this project.
Install each one with: npx shadcn@latest add https://get-neonkit.vercel.app/r/<name>.json
Check the component's .md page for its props before using it.