Documentation
Start with a component, connect your agent or check a requirement. The guides cover setup and adaptation; the references explain the exact file and tool contracts.
Start here
The requirements each component declares, the Tailwind setup they need, and how to add your first one.
3 documents
Getting started
What these components are, what your project needs, and how to add your first component.
Understand component requirements
The declarations every published component makes about its runtime, integration level, dependencies, services, files and release state.
Tailwind prerequisites
How to configure Tailwind CSS 4 so the utility classes in copied components are generated.
Using components
Getting a component’s source, adapting it, and what it needs from your project once it is in.
5 documents
Get component source
The ways to retrieve a component's source for one exact version and variant, and how to verify what you received.
Customization
How palettes, variants and CSS variables work, and when to edit component source directly.
Dependencies and assets
How components declare third-party packages, external services and bundled assets, and what you need to install or provide.
SvelteKit recipes
How integration levels separate presentational components from SvelteKit integration recipes, and what a recipe asks of your project.
Accessibility in your project
What each component documents about accessibility, and what remains your responsibility once it is in your site.
Agents and API
How coding agents find and fetch components: the MCP server, the public API, the bundle format and Markdown twins.
5 documents
MCP reference
The MCP server's endpoint, tools, limits, version rules, errors and privacy notes, with setup for each coding agent on the MCP page.
Agent workflow
A practical sequence for coding agents that select, retrieve and integrate catalogue components into a Svelte project.
Public API
The public routes, filter vocabulary, limits and error codes shared by the website, the HTTP API and the MCP server.
Distribution format
The distribution receipt, how file hashes and the artifact digest are computed, and the layout of a component bundle.
Markdown for agents
Every page has a Markdown twin: append .md to any path, or start from llms.txt, and read the catalogue without parsing HTML.
Policies and support
How components are licensed, and how to report a problem.
2 documents
License
How component source and asset licenses are declared, and the current status of the default license and website content terms.
Help and issue reports
What to include when you report a problem with a component, the documentation or the catalogue services, and where to send it.