Skeleton

Skeleton is no longer Svelte-only. It now ships parallel documentation and packages for Svelte and React, sitting on a shared Tailwind design token layer that works with or without components.

At a glance

Install	npm install @skeletonlabs/skeleton
Frameworks	Svelte and React
Styling	Tailwind with a design token system
Themes	multiple presets, plus a theme generator
MCP server	not published, llms.txt available
License	MIT

Install

The token layer is imported in CSS, not configured in JavaScript:

@import 'tailwindcss';
@import '@skeletonlabs/skeleton';
@import '@skeletonlabs/skeleton/themes/cerberus';

The tokens are the point

Skeleton's design tokens are Tailwind classes, so the theme applies to your own markup exactly as it does to Skeleton's components. Change theme and everything follows, including elements the library never touched.

<button class="btn preset-filled-primary-500">Save</button>
<div class="card preset-tonal p-4">
  <h3 class="h3">Deployment</h3>
</div>

That is a meaningfully different bargain from a component library: you can adopt the design system without adopting the components.

Choose it if

• You want a themable Tailwind foundation rather than a closed component set.
• You ship Svelte and React and want one visual language across both.
• You want a theme you can regenerate rather than hand-tune.

Look elsewhere if

• You need documented WAI-ARIA conformance per component. Bits UI is stronger there.
• You are not on Tailwind. The token system is the library.