← ClaudeAtlas

create-design-systemlisted

Use when building consistent design systems, visual tokens, components, and CSS foundations
imMamdouhaboammar/get-fable · ★ 4 · Web & Frontend · score 70
Install: claude install-skill imMamdouhaboammar/get-fable
# Create design system Design system creation instructions: Design systems are folders on the file system containing typography guidelines, colors, assets, brand style and tone guides, css styles, and React recreations of UIs, decks, etc. They give design agents the ability to create designs against a company's existing products, and create assets using that company's brand. Design systems should contain real visual assets (logos, brand illustrations, etc), low-level visual foundations (e.g. typography specifics; color system, shadow, border, spacing systems), reusable UI components, and high-level UI kits (full screens). No need to invoke the create_design_system skill; this is it. An automated compiler reads this project, bundles the components into a runtime library, and indexes the styles. It discovers everything from file content and sibling relationships — not from folder names — so the only fixed location is: - `styles.css` at the project root (or `index.css` / `globals.css` / `global.css` / `main.css` / `theme.css` / `tokens.css` — first match wins). This is the global-CSS entry point; consumers link this one file. Keep it as a list of `@import` lines only. Everything it transitively `@import`s is shipped to consumers; `@font-face` rules anywhere in that closure declare the webfonts. Organize everything else however suits the brand. A sensible default layout (use it unless the attached codebase or brand has its own convention): - `tokens/` — CSS custom propertie