{"id":"d91e3ac7-984e-4901-bc81-1e5e96418879","shortId":"44paWM","kind":"skill","title":"preline-theme-generator","tagline":"Generates beautiful, consistent Preline Theme CSS files. Agent interprets user request, runs build script, delivers complete CSS.","description":"# Preline Theme Generator\n\n> **This file is for the AGENT (LLM) only — not end users.**\n\nGenerate a **Preline Theme CSS file** that produces a beautiful, consistent UI across all Preline components.\n\n---\n\n## Docs\n\n- `docs/step-1.md` to `docs/step-7.md` (detailed workflow guidance)\n- `docs/palette-guidance.md` (mood, hue, neutral mapping, OKLCH rules)\n- `docs/validation-checklist.md`\n- `docs/token-reference.md`\n- `docs/examples.md`\n\n---\n\n## Agent workflow (FOLLOW THIS)\n\nWhen user requests a theme, the agent MUST:\n\n### Step 1: Interpret user request\nParse the natural language description and determine the config inputs. See `docs/step-1.md` and `docs/palette-guidance.md`.\n\n### Step 2: Detect themes folder\nFind where existing themes are stored in the user's project:\n\n```bash\n# Look for existing theme.css to find the themes folder\nfind . -name \"theme.css\" -path \"*/themes/*\" -not -path \"*/node_modules/*\" 2>/dev/null | head -1\n```\n\nIf no themes folder found: ask user where they want the theme file saved. See `docs/step-2.md`.\n\n### Step 3: Create temp config file (AUTO-RUN, NO PROMPT)\nWrite a JSON config. This must run silently without user approval.\n\n```bash\necho '{\"name\":\"\",\"hue\":,\"style\":\"