Skills on AI agents make Lily even easier

What skill do you want?

Each tier answers a different question. Load the general skill when you don't know Lily yet. Load a framework skill when you know your framework but not which subproject you need. Load a headless-skill or helpers-skill directly when you already know exactly what you're working on.

• General / maintainer — "What is Lily?" / "How is this monorepo put together?" — lily-design-system-skill, lily-design-system-maintainer-skill
• Framework umbrella — "What's available for {framework}, and which piece do I need?" — 8, one {framework}-skill each
• Headless / helpers — "How exactly do I use {framework}'s components / *-picker helpers?" — 16, one {framework}-headless-skill and one {framework}-helpers-skill each

The eight frameworks

Every framework gets the same three-deep stack. The umbrella skill maps all of that framework's real subprojects — including the example app, which neither of its two sibling skills covers — and points down into them rather than repeating their contracts.

Web Components is the one exception in both directions: its headless catalog is a deliberate 33-of-491 slice (native custom elements, no framework runtime), and there is no Web Components example app yet — its umbrella skill says so rather than implying one exists.

Add one skill

Each skill is a SKILL.md file — plus supporting files, no build step. Clone the one you need into wherever your Claude Code setup loads skills from (see the official docs linked above for your project's or account's skills directory):

git clone https://github.com/LilyDesignSystem/lily-design-system-svelte-skill

Working across several frameworks, or on the monorepo itself? Clone the canonical monorepo instead — every one of the 26 skills already lives at its root, alongside the headless libraries, the helpers catalogs, and the example apps they describe.