human-optimized-frontend

3
1
Source

Generates a frontend interface that is visually pleasing and experientially sound by jointly optimizing aesthetics, motion graphics, and user experience (UX) using quantified evaluation. Use only when the user explicitly invokes this skill by name to redesign a frontend. Trigger keywords: use human-optimized-frontend, redesign frontend, redesign interface.

Install

mkdir -p .claude/skills/human-optimized-frontend && curl -L -o skill.zip "https://mcp.directory/api/skills/download/6488" && unzip -o skill.zip -d .claude/skills/human-optimized-frontend && rm skill.zip

Installs to .claude/skills/human-optimized-frontend

About this skill

Activation Criteria

Activate this skill only when the user explicitly instructs the agent to redesign a frontend and references this skill by name.

Do not activate for:

  • Conceptual discussion or critique only
  • Coding or implementation tasks
  • Inspiration, references, or visual examples
  • Partial or component-level design requests

Execution Steps

1. Context Intake

  • Consume all provided information about the interface.
  • If context is missing, assume a neutral functional product with general-purpose usage.
  • Do not assume branding, audience psychology, or business goals unless explicitly stated.

2. Direction Lock (Aesthetic + UX)

  • Select exactly one aesthetic direction.
  • Select exactly one UX interaction philosophy (e.g. clarity-first, flow-driven, exploration-led).
  • All visual, motion, and interaction decisions must reinforce both.
  • Do not mix stylistic or interaction paradigms.

3. Initial Design Generation

Typography

  • Body text baseline: 15–18px equivalent
  • Heading scale:
    • H1 = body × 2.2–2.6
    • H2 = body × 1.6–1.9
    • H3 = body × 1.3–1.5
  • Line height:
    • Body: 1.45–1.6
    • Headings: 1.15–1.3
  • Font rule:
    • Serif + sans-serif pairing OR single family with ≥ 4 weights
  • Letter spacing:
    • Headings: -1% to -3%
    • Body: 0% to +1%
  • Prohibited fonts: system defaults, Inter, Roboto, Arial.

Color & Theme

  • Palette:
    • 1 dominant
    • 1 secondary
    • 1 accent
    • 1 neutral base
  • Contrast:
    • Text ≥ 4.5:1
    • Interactive elements ≥ 3:1
  • Accent usage ≤ 10% of visible area
  • Only one saturated color allowed
  • Gradients allowed only as background fields

Layout & Composition

  • Single spacing base unit (8px or 10px)
  • Visual weight distribution:
    • Primary: 40–55%
    • Secondary: 25–35%
    • Tertiary: ≤ 20%
  • Maximum two alignment axes per view
  • Symmetry allowed only with counterbalancing contrast

Background & Depth

  • Background type:
    • Textured neutral OR
    • Low-contrast geometry OR
    • Layered planes
  • Max depth layers: 3
  • Foreground contrast must exceed background by ≥ 20%

Motion Graphics (Mandatory)

  • Required motion categories:
    • Entry motion
    • Hierarchy reinforcement
    • Interaction feedback
  • Timing: 180–420ms
  • Easing:
    • Primary: ease-out
    • Secondary: subtle cubic or linear
  • Max simultaneous moving elements per viewport: 3
  • Motion must encode hierarchy, state, or spatial relation
  • Prohibited: decorative loops, idle animations, novelty motion

UX Structure (Mandatory)

  • Define a primary user goal per view.
  • All visual and motion emphasis must support this goal.
  • Interaction rules:
    • One primary action per screen
    • Secondary actions visually subordinate
  • Navigation clarity:
    • Entry point must be obvious within 1 second
    • Next available action must be discoverable without exploration
  • Cognitive load:
    • No more than 3 competing focal points per view
  • Feedback:
    • All user actions must produce immediate visual or motion feedback
  • Error tolerance:
    • Interfaces must be forgiving; destructive actions must be visually distinguished

4. Quantitative Evaluation Loop

Score each dimension from 0–10:

Typography

  • ≥ 8: hierarchy instantly readable
  • ≤ 6: scale or spacing feels inconsistent

Color

  • ≥ 8: dominance and emphasis are unambiguous
  • ≤ 6: accents compete or contrast is weak

Layout

  • ≥ 8: eye flow resolves within 1–2 seconds
  • ≤ 6: multiple regions compete equally

Background

  • ≥ 7: depth supports hierarchy
  • ≤ 5: background distracts or feels empty

Motion

  • ≥ 8: motion improves comprehension and flow
  • ≤ 6: motion distracts or delays intent

UX

  • ≥ 8: user intent is obvious, actions feel effortless
  • ≤ 6: hesitation, ambiguity, or friction introduced

Cross-Dimensional Harmony

  • ≥ 8: visuals, motion, and UX reinforce the same hierarchy and intent
  • ≤ 6: any dimension contradicts another

Weighted Total Score

  • Typography: 20%
  • Color: 20%
  • Layout: 20%
  • Motion: 15%
  • UX: 15%
  • Background: 10%
  • Harmony: mandatory ≥ 8

5. Iteration Rules

  • Adjust lowest-scoring dimension first.
  • UX adjustments take priority if UX score < 8.
  • Never adjust more than two dimensions per iteration.
  • Maximum iterations: 5.
  • If harmony score drops, revert the last change.

6. Final Output

Produce a single declarative frontend specification including:

  • Typography system
  • Color palette with roles
  • Layout structure and visual weights
  • Background and depth treatment
  • Motion graphics definitions
  • UX flow and interaction rules

No alternatives. No explanations. No theory.

Ambiguity Handling

  • Missing context defaults to neutral functional usage.
  • Defaults must still satisfy aesthetic, motion, and UX thresholds.
  • Never infer branding, emotional tone, or audience psychology.

Constraints & Non-Goals

  • Do not generate code, assets, or mockups.
  • Do not critique existing designs unless redesign context requires it.
  • Do not reference trends, competitors, or popular products.
  • Do not provide multiple options.
  • Do not justify decisions.

Failure Behavior

If activation conditions are not met, output a minimal statement indicating the skill cannot be activated.

If after maximum iterations UX or harmony thresholds are not met, output a minimal statement indicating that a satisfactory frontend cannot be generated under the given constraints and terminate.

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

1,6851,428

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

1,2681,335

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

1,5381,147

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

1,356809

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

1,264728

pdf-to-markdown

aliceisjustplaying

Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.

1,489684