Documentation

Start here

Getting started

What these components are, what your project needs, and how to add your first component.
Component contract

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.

Source acquisition

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 responsibilities

What each component documents about accessibility, and what remains your responsibility once it is in your site.

MCP reference

Technical reference for the MCP server. Its endpoint, tools, limits, version rules, errors and privacy notes. Setup steps for each coding agent are 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.

License

How component source and asset licenses are declared, and the current status of the default license and website content terms.
Reporting issues

What to include when you report a problem with a component, the documentation or the catalogue services, and where to send it.