Frontend Design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifact...

Security Scan

The skill is an instruction-only frontend design helper whose requirements and instructions are consistent with its stated purpose; no unexpected credentials, installs, or privileged behavior are requested.

Purpose & Capability

Name and description match the SKILL.md content: the skill focuses on producing visual/frontend code (HTML/CSS/JS, React, Vue) and design guidance. It does not request unrelated binaries, credentials, or cloud access, which is proportionate for a design/code-generation skill.

Instruction Scope

The instructions are detailed and constrained to frontend design and code generation. They explicitly state code will be written into the user's specified project directory and that no external credentials or network access are required. Minor inconsistency: SKILL.md references a LICENSE.txt but no LICENSE file is present in the manifest — the absence of that file is a documentation gap, not a functional risk. Also note: the guidance encourages choosing distinctive fonts and libraries; using certain fonts or assets may require the agent (or the user) to add external font files or CDN links — the skill does not itself fetch or require them.

Install Mechanism

No install spec and no code files are present (instruction-only). This is the lowest-risk model: nothing is downloaded or written by an installer. All runtime behavior is agent-driven generation of code outputs.

Credentials

The skill requests no environment variables, credentials, or config paths. That is appropriate for a frontend design/code-generation skill that does not integrate with external services.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request persistent platform privileges. The agent will generate files in the user's specified project directory when run (normal for this skill type).

Assessment

This skill is coherent for generating frontend code and design guidance. Before using it: (1) confirm the exact project directory/path you want the agent to write into and review any files it creates; (2) if you require specific fonts or licensed assets, provide them or specify acceptable free fonts—generated code may include font links or require adding files manually; (3) note the SKILL.md references a LICENSE.txt that isn’t in the package—ask the maintainer for licensing terms if that matters; and (4) always review produced code (dependencies, build scripts, and external CDN links) before deploying to production.

Triggers

Activate this skill when the user asks to:

• Build a web component, page, application, or interface
• Create a landing page, dashboard, or portfolio
• Style or beautify an existing web UI
• Generate HTML/CSS/JS, React, Vue, or similar frontend code
• Design a poster, card, or visual artifact for the web

NOT For

• Backend logic — APIs, databases, server routes, authentication; use coding tools directly
• Data modeling — schema design, ORM configuration, data pipelines
• CLI or terminal UIs — this skill is for browser/web interfaces only
• Infrastructure or deployment — Docker, CI/CD, cloud configs

Decision Rules

1. If the request is purely visual/UI → follow this skill fully (design thinking + aesthetic guidelines)
2. If the request mixes frontend + backend → handle frontend with this skill; handle backend separately
3. If the user specifies a framework (React, Vue, Svelte) → use it; otherwise default to clean HTML/CSS/JS
4. If the user specifies an aesthetic → follow their direction; otherwise commit to a bold, unexpected choice
5. If the artifact is small (single button, one card) → skip the design thinking step, implement directly

---

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.

All generated code is written within the user's specified project directory. No external services, credentials, or network access are required.

The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.

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?

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:

• Production-grade and functional
• Visually striking and memorable
• Cohesive with a clear aesthetic point-of-view
• Meticulously refined in every detail

Frontend Aesthetics Guidelines

Focus on:

• Typography: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
• Color & Theme: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
• Motion: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
• Spatial Composition: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
• Backgrounds & Visual Details: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.

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.

IMPORTANT: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.

Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.