# wlilo-design-system > Use when you need the WLILO look (White Leather + Industrial Luxury Obsidian) across HTML, SVG, and jsgui3. Covers token schema, palette, and how to write back design learnings so other agents reuse them. Triggers: wlilo, white leather, industrial luxury, obsidian, design system, palette, theme tokens, diagram styling. - Author: metabench - Repository: metabench/copilot-dl-news - Version: 20260118094258 - Stars: 1 - Forks: 0 - Last Updated: 2026-02-06 - Source: https://github.com/metabench/copilot-dl-news - Web: https://mule.run/skillshub/@@metabench/copilot-dl-news~wlilo-design-system:20260118094258 --- --- name: wlilo-design-system description: "Use when you need the WLILO look (White Leather + Industrial Luxury Obsidian) across HTML, SVG, and jsgui3. Covers token schema, palette, and how to write back design learnings so other agents reuse them. Triggers: wlilo, white leather, industrial luxury, obsidian, design system, palette, theme tokens, diagram styling." --- # Skill: WLILO Design System (White Leather + Industrial Luxury Obsidian) ## WLILO acronym WLILO = **White Leather + Industrial Luxury Obsidian**. ## Scope Use this Skill to: - Apply WLILO consistently across **HTML/CSS**, **inline/build-time SVG**, and **jsgui3** controls. - Convert “make it feel WLILO” into a small, repeatable **token set**. - Improve repo memory: when you learn a reusable design rule, **write it back** (Skills/Patterns/Lessons). Out of scope: - Pixel-perfect design reviews (ask for screenshots / run capture scripts when needed) - Large rebrands (create a dedicated design session) ## Inputs - Target surface: `html`, `svg`, `jsgui3` (one or more) - Embedding mode for SVG: `file/img` (build-time variants) vs `inline` (CSS variables possible) - Constraints: contrast/readability, collision-free diagrams, performance (control counts) ## Procedure ### 0) Memory load + user-visible feedback (required) 1. Read: - `docs/guides/WLILO_STYLE_GUIDE.md` 2. If the task is SVG heavy, also read: - `docs/agi/skills/svg-theme-system/SKILL.md` - `docs/agi/skills/svg-collisions/SKILL.md` Then emit a 1–2 line summary so the user can see what you loaded: - `🧠 Memory pull (for this task) — Skills=wlilo-design-system, svg-theme-system | Sessions= hits | Guides=WLILO_STYLE_GUIDE | I/O≈` - `Back to the task: ` ### 1) Use a small token schema (don’t freestyle colors) Recommended tokens (minimum viable): - `--wlilo-bg` (leather) - `--wlilo-panel` (obsidian) - `--wlilo-border` (panel border) - `--wlilo-text` / `--wlilo-text-muted` - `--wlilo-accent-gold` - `--wlilo-accent-blue` (optional CTA) Reference palette values live in `docs/guides/WLILO_STYLE_GUIDE.md`. ### 2) Apply tokens per surface **HTML/CSS (recommended default)** - Define tokens in `:root` (or a theme scope class). - Apply WLILO via semantic classes (panels, headers, separators) rather than per-element inline styles. **SVG** - If SVG is used via `` / markdown: prefer **build-time variants** (one SVG per theme). - If SVG is inlined: define CSS variables inside `