frontend-design

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.

Gotchas and Scope Gate

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.

Design Thinking

Before coding, understand the context and commit to a BOLD aesthetic direction:

• Purpose: What problem does this interface solve? Who uses it?
• Tone: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
• Constraints: Technical requirements (framework, performance, accessibility).
• Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?