Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/frontend-design
Create distinctive, production-grade frontend interfaces with high design quality.
Passed 15 of 22 test cases with the skill, and 11 of 22 without it.
and 3 more in the full report
6 fixed9 passed either way5 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Can you build a responsive web interface for a high-frequency trading analytics dashboard? I need HTML, CSS, and JavaScript for a telemetry screen that displays live market order books, price movement charts, and risk alert metrics. Deliver fully functional, production-ready code for browser rendering.
| Checked | Without skill | With skill |
|---|---|---|
| The CSS font-family declaration explicitly excludes system font fallbacks like -apple-system or BlinkMacSystemFont as primary display choices | Missed | Passed |
| The styling defines specific custom typography rather than defaulting to generic font families like Roboto or Arial | Passed | Passed |
The instructions your model reads when the skill loads.
This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
Use this skill only when the implementation target is a web frontend. Before applying its aesthetics guidance, verify that the relevant code is HTML/CSS/JavaScript or a web UI framework.
Stop using this skill if repository inspection shows that the visual surface is implemented by a native renderer, GPU shader, game engine, terminal UI, video pipeline, or another non-web graphics stack. Route that work to the relevant language, rendering, or visual-verification workflow instead. A request to make something look more polished does not establish web-frontend scope.
Trigger regression cases live in evals/triggers.jsonl.
Before coding, understand the context and commit to a BOLD aesthetic direction:
CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
Focus on:
NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
test cases passed, vs 11 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.