frontend-design

Bespoke frontend engineering focused purely on aesthetic excellence. Invoke for web components, pages, dashboards, applications, or any UI requiring distinctive visual execution. Outputs functional code with intentional aesthetic direction and creative craft.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "frontend-design" with this command: npx skills add ilm-alan/frontend-design/ilm-alan-frontend-design-frontend-design

Frontend Design Skill

Core Thesis

Great frontend design is disciplined translation: a clear, context-specific aesthetic intent (archetype + one differentiator) translated into a coherent system of typography, color tokens, layout, motion, and texture.


1. Operating Mode

Before writing code, complete this sequence:

  1. Context: Identify purpose, users, domain, and content density. Output a clear problem statement.
  2. Aesthetic Direction: Select one archetype from Section 2 and state it explicitly.
  3. Differentiator: Define one memorable anchor—a signature interaction, typographic move, layout motif, texture, or material treatment.
  4. System: Define tokens and rules: type scale, spacing rhythm, palette mapping, elevation levels.
  5. Implementation: Outline structure and interaction model, then build.

Directive: Commit fully to the chosen direction. Do not average multiple styles into a bland middle. Hybridize only when you can articulate the governing rule for the hybrid.


2. Aesthetic Archetypes

Select one archetype as the foundation:

  • Editorial / Magazine: Strong typographic hierarchy, generous whitespace, refined grid. Use pull quotes, drop caps, column layouts, and serif display type.
  • Swiss / International: Geometric precision, sans-serif dominance, systematic spacing. Apply strict grids, Akzidenz/Helvetica lineage typefaces, and asymmetric balance.
  • Brutalist / Raw: Exposed structure, high contrast, anti-decorative. Embrace monospace type, visible borders, system UI elements, and raw HTML aesthetic.
  • Minimalist / Refined: Restraint, micro-contrast, meticulous spacing. Deploy limited palettes, ample whitespace, subtle shadows, and precise alignment.
  • Maximalist / Expressive: Layered composition, bold color, dynamic motion, visual density. Use overlapping elements, animated gradients, and complex grid breaks.
  • Retro-Futuristic: Nostalgic UI cues, neon accents, CRT aesthetics. Apply scanlines, glitch effects, terminal green, pixel fonts, and glow.
  • Organic / Natural: Soft geometry, earthy palettes, tactile texture. Incorporate rounded shapes, grain overlays, hand-drawn elements, and warm tones.
  • Industrial / Utilitarian: Functional aesthetic, monochrome, dense grids. Build data-heavy layouts with instrument-panel vibes and no ornamentation.
  • Art Deco / Geometric: Symmetry, metallic accents, ornamental precision. Use fan shapes, gold/brass tones, decorative borders, and Gatsby-era typography.
  • Lo-Fi / Zine: Rough textures, collage aesthetic, deliberate imperfection. Apply torn edges, mixed type, print artifacts, and halftone/duotone effects.

3. Technical Implementation

3.1 Typography

Choose context-appropriate typefaces that reinforce the archetype—avoid defaults like Arial, Inter, Roboto, and system stacks. Establish hierarchy through a distinct display/body pairing, using size, weight, case, and spacing to create 3–5 clear levels.

Use clamp() for fluid responsive scaling (e.g., font-size: clamp(1rem, 2.5vw, 1.5rem)). Tune line-height carefully: 1.4–1.6 for body text, 1.1–1.2 for display type. Adjust letter-spacing and font-feature-settings for refinement.

3.2 Color System

Structure your palette with CSS custom properties: --color-surface, --color-text, --color-muted, --color-primary, --color-accent, --color-border. Add semantic tokens for feedback states: --color-success, --color-warning, --color-error.

Distribute color intentionally—dominant (60%) + supporting (30%) + accent (10%). Avoid timid, evenly-split palettes.

Implement theme support via prefers-color-scheme media query or explicit class toggle.

3.3 Motion & Interaction

Motion must communicate state, hierarchy, or affordance—never decoration alone. Use custom cubic-bezier() timing functions; avoid linear for UI transitions. Orchestrate page-load sequences with staggered animation-delay offsets (50–100ms increments).

Use IntersectionObserver for scroll-triggered animations. Prefer CSS for HTML/vanilla JS projects. Use Motion (Framer Motion) for React/Vue when available.

3.4 Spatial Composition

Use CSS Grid for 2D layouts and Flexbox for linear distribution. Define a consistent spacing scale with custom properties: --space-xs, --space-sm, --space-md, --space-lg, --space-xl.

Treat whitespace as a structural element, not leftover space. Create hierarchy through dramatic scale contrast (e.g., 4:1 heading-to-body ratio).

Break the grid intentionally—overlap elements with position: absolute/relative and z-index for purposeful disruption. Use asymmetric alignments to create visual tension; avoid defaulting to center alignment. Deploy full-bleed moments that break container boundaries for emphasis using viewport units.

3.5 Visual Depth & Texture

Build layered shadows with multiple box-shadow values using varying blur/spread for realistic depth. Define elevation levels: --shadow-sm, --shadow-md, --shadow-lg.

For glassmorphism, use backdrop-filter: blur() with semi-transparent backgrounds (check browser support). Add noise and grain via SVG <feTurbulence> filter or CSS background-image with texture overlay.

Create gradients with intention—mesh gradients, radial compositions, multi-stop configurations. Avoid generic purple→blue linear gradients.

Use clip-path: polygon() or circle() for non-rectangular shapes. Design borders and dividers with decorative intent, including custom border-image and creative separators that match the archetype.

Apply texture overlays appropriate to the style: halftone, duotone, or stipple for print aesthetics; scanlines for retro-futuristic.


4. Anti-Patterns

Explicitly avoid these markers of generic output:

Typography: Never use system font stacks, Inter/Roboto/Arial, or uniform sizing. Instead, choose distinctive, context-appropriate typefaces with clear hierarchy.

Color: Avoid purple-on-white gradients, evenly distributed palettes, and low contrast. Instead, commit to palettes with dominant/accent distribution.

Layout: Reject centered card grids and predictable hero→cards→testimonials→footer structures. Instead, use asymmetric compositions, unexpected grid breaks, and purposeful whitespace.

Motion: Eliminate gratuitous animations, linear easing, and motion without purpose. Instead, use purposeful transitions, custom easing, and orchestrated sequences.

Details: Replace stock illustrations and generic icons with bespoke graphics, custom iconography, and contextual imagery.

Structure: Make every visible element intentional. Transform any generic scaffolding into something that reinforces the aesthetic direction.


5. Output Contract

Every implementation must deliver:

  • Stated Direction: Explicitly name the archetype and differentiator in 1–2 lines before code.
  • Working Code: Functional code that demonstrates the aesthetic direction.
  • Design Tokens: CSS custom properties for colors, spacing, typography, and shadows.
  • Responsiveness: Demonstrated via fluid layout, breakpoints, or container queries.

6. Finish Checklist

Before delivering, verify:

  • Archetype Fidelity: Does every visual choice reinforce the stated archetype?
  • Differentiator: Is the memorable anchor implemented, not just described?
  • Token Coherence: Are typography, spacing, and color tokens consistent throughout?
  • Responsive Behavior: Does it remain intentional on mobile, tablet, and wide desktop?
  • Template Smell: Is there any generic scaffolding remaining? Transform it.

Intention in every choice. Precision in every detail. Nothing left to default.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

Repository SourceNeeds Review
162.2K94.2Kanthropics
Coding

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.

Repository Source
14.9K9Kpbakaus
Coding

frontend-design

No summary provided by upstream source.

Repository SourceNeeds Review
1.2K-am-will
Coding

frontend-design

No summary provided by upstream source.

Repository SourceNeeds Review