Skills for AI agents make Lily even easier

Which skill you want?

Each tier answer different question. Load di general skill when you no know Lily yet. Load framework skill when you know your framework but you no know which subproject you need. Load headless-skill or helpers-skill directly when you already know exactly wetin you dey work on.

• General / maintainer — “Wetin be Lily?” / “How dem put dis monorepo together?” — lily-design-system-skill, lily-design-system-maintainer-skill
• Framework umbrella — “Wetin dey available for {framework}, and which piece I need?” — 8, one {framework}-skill each
• Headless / helpers — “How exactly I go use {framework} components / *-picker helpers?” — 16, one {framework}-headless-skill and one {framework}-helpers-skill each

Di eight frameworks

Every framework get di same three-deep stack. Di umbrella skill dey map all di real subprojects of dat framework — including di example app, wey neither of im two sibling skills cover — and e dey point down enter dem instead of to repeat dia contracts.

Web Components na di one exception for both directions: im headless catalog na deliberate 536-of-571 scope (native custom elements, no framework runtime; di other 35 components dem permanently exclude), and no Web Components example app dey yet — im umbrella skill talk so instead of to imply say one dey.

Add one skill

Each skill na SKILL.md file — plus supporting files, no build step. Clone di one wey you need enter wherever your Claude Code setup dey load skills from (see di official docs wey dem link above for your project or account skills directory):

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

You dey work across several frameworks, or for di monorepo itself? Clone di canonical monorepo instead — all 26 skills already dey for im root, beside di headless libraries, di helpers catalogs, and di example apps wey dem describe.