Individual skill
frontend-design
Create distinctive, production-grade frontend interfaces with top-tier product design and UI/UX quality. Use this skill when the user asks to build web components, pages, or applications. Combines product thinking, UX discipline, and creative visual design.
skills/frontend-design/SKILL.md
Source commit ed232cba00040a3a8294aff08d14a0053cb8a0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 123
- Repository last updated
- Jul 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- claude Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- code-review Repository topic
- developer-tools Repository topic
- indie-hackers Repository topic
- lighthouse Repository topic
- performance Repository topic
- playwright Repository topic
- design Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 17,245 bytes
Read excerpt
This skill combines three disciplines: **product design** (does it solve the right problem?), **UX design** (can users accomplish their goals without friction?), and **visual design** (is it distinctive and polished?). All three must be present. Beautiful but unusable is a failure. Usable but ugly is a failure. Both beautiful and usable but solving the wrong problem is the worst failure.
The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
## Product Design Thinking
Before touching aesthetics, think like a product designer:
**1. User Intent**
- What is the user trying to accomplish on this page/component?
- What is the ONE primary action? (every screen has one — if you can't identify it, the design is confused)
- What information does the user need to make a decision? Show that, hide everything else.
**2. Information Hierarchy**