agents/skills/frontend-design/SKILL.md
Design and implement distinctive, production-ready frontend interfaces with strong aesthetic direction. Use when asked to create or restyle web pages, components, or applications (HTML/CSS/JS, React, Vue, etc.).
npx skillsauth add elianiva/dotfiles frontend-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design and implement memorable frontend interfaces with a clear, intentional aesthetic. The output must be real, working code — not just mood boards. This skill is about design thinking + execution: every visual choice should be rooted in purpose and context.
Use this skill when the user wants to:
Before coding, identify:
If the user did not provide this, ask 2–4 targeted questions, or state reasonable assumptions in a short preface.
Commit to a single, bold aesthetic direction. Name it and execute it consistently. Examples:
Avoid generic AI aesthetics. No “default” fonts, color schemes, or stock layouts.
Before writing code, define the system:
If the user wants code only, skip the explanation but still follow this internally.
prefers-reduced-motionRemember: a design is only as strong as its commitment. Choose a direction and execute it relentlessly.
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
development
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
tools
At end of difficult sessions, analyze friction points and propose concrete improvements.
testing
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior