frontend-design

Generates distinctive visual design guidance for building or reshaping web UI.

1|Updated Jul 6, 2015
One-click install
npx skills add https://github.com/ksolomon/dotfiles --skill frontend-design-ksolomon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-design
Source: https://github.com/ksolomon/dotfiles/tree/main/AI/.claude/plugins/marketplaces/claude-plugins-official/plugins/frontend-design/skills/frontend-design
Command: npx skills add https://github.com/ksolomon/dotfiles --skill frontend-design-ksolomon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated web designs tend to cluster around a few templated looks, producing pages that read as generic defaults rather than intentional choices. This Skill provides a structured design methodology that grounds palette, typography, layout, and copy in the specific subject of each brief. ## Core Features & Use Cases - Subject-Grounded Direction: Pins down the product, audience, and page purpose before designing, deriving visual choices from the subject's own world and materials. - Two-Pass Design Process: Brainstorms a compact token system (color, type, layout, signature element), critiques it against generic defaults, then builds code strictly from the revised plan. - Interface Copywriting Guidance: Applies the same intentionality to words as to spacing and color, covering active voice, error states, empty states, and consistent action naming. - Use Case: When asked to build a landing page for a new product, use this Skill to produce a design plan with named hex palette, paired typefaces, an ASCII wireframe, and one signature element before writing any HTML or CSS. ## Quick Start Use the frontend-design skill to create a distinctive landing page design for my product, starting with a design plan before writing any code.

Frequently Asked Questions about frontend-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI-generated web designs look less templated?▼

Ground every design choice in the specific subject of the brief rather than reaching for default palettes and layouts. Plan a token system with named colors, paired typefaces, and one signature element, then critique the plan against generic defaults before writing code.

What is a good process for planning a web page design before coding?▼

Work in two passes: first brainstorm a compact plan covering color palette, type scale, layout concept with ASCII wireframes, and a signature element. Then review the plan for generic choices, revise it, and only then write code following the revised plan exactly.

How should typography be handled in web UI design?▼

Pair display and body typefaces deliberately for each project rather than reusing familiar families. Set a clear type scale with intentional weights, widths, and spacing so the type treatment itself becomes a memorable part of the design.

When should animation be used in web page design?▼

Use animation only where it serves the subject, such as a page-load sequence, scroll-triggered reveal, or hover micro-interactions. One orchestrated moment usually lands harder than scattered effects, and excess animation can make a design feel AI-generated.

What are common AI-generated design defaults to avoid?▼

Three common defaults are a warm cream background with serif display and terracotta accent, a near-black background with acid-green accent, and a broadsheet layout with hairline rules. These are legitimate when a brief requests them, but should not be automatic choices.

How do I write better interface copy for web designs?▼

Write from the end user's perspective using active voice, naming controls by what people do rather than how the system works. Treat errors and empty states as moments for direction, keep the register conversational, and let each element do exactly one job.