Frontend design skill for distinctive production-grade interfaces

Prerequisites: a frontend project or UI request to apply it to — the skill is design guidance the agent follows, not software to install Install "Frontend design skill for distinctive production-grade interfaces" for me. It gives my agent Cline's frontend-design workflow: design thinking first (understand context — purpose, audience, constraints), pick a bold aesthetic direction, commit to it with precision, then implement real working code (HTML/CSS/JS, React, Vue) — distinctive typography (never Arial/Inter/system fonts by default), cohesive color with sharp accents, CSS-first motion, unexpected spatial composition, atmospheric backgrounds — with a never-do list (overused fonts, purple gradients on white, predictable layouts). Apache-2.0 licensed. Repository: https://github.com/cline/skills/blob/main/skills/frontend-design/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "frontend-design". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the UI to build or redesign; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.