Design Web
Build websites that look like a designer made specific choices for this subject, not like a template with the words swapped. Polish comes from consistency and restraint far more than from effects, so favor a small number of well-executed decisions over many decorative ones.
Work in three passes
- Plan. Decide the direction before writing code (see below).
- Build. Implement the plan with design tokens, so every color, size, and space comes from one system.
- Review. Critique the result against the checklist at the end, and fix what falls short.
If the user's brief names a style, palette, font, or layout, follow it exactly. Their words always win over the defaults in this skill.
1. Plan before code
Write a short plan covering:
- Subject, audience, and job. What is this site, who visits, and what should they do? If the brief doesn't say, propose one in a sentence and state that you assumed it. Distinctive choices come from the subject's own world (its materials, vocabulary, and mood), so a ceramics studio and a fintech dashboard should look nothing alike.
- Aesthetic direction. Pick one (editorial minimal, soft SaaS, brutalist, playful, technical, warm and crafted) and commit to it, with a one-line reason tied to the subject.
- Tokens. Four to six named colors as hex values, the typefaces and their roles, the spacing unit, the radius scale, and the shadow style.
- Hero idea. Open with the most characteristic thing in the subject's world: a strong headline, a live demo, a striking image or illustration, an interactive moment.
Then check the plan against the brief. If a part of it is what you would produce for any similar request, change that part and note what you changed. A generic plan produces a generic site.
2. Design system
Color
- Define the palette as CSS custom properties on
:root: a neutral scale (background, surface, border, muted text, text), one primary accent, and optionally one secondary. - Support light and dark with
prefers-color-schemeby redefining the tokens, not by overriding individual rules. - Use the accent sparingly, for primary actions and one or two highlights, so it keeps its meaning.
- Keep contrast at 4.5:1 for body text and 3:1 for large text and UI borders.
Typography
- Use at most two families. If two, give them clearly different roles (a display face for headlines, a text face for reading).
- Choose faces for this subject rather than the first default that comes to mind, and load web fonts with
font-display: swapand a full fallback stack. - Build a type scale (ratio around 1.2 to 1.333) and make headlines fluid with
clamp(). - Set headlines tight (line-height 1.05 to 1.15, slightly negative letter-spacing at large sizes) and body text open (16 to 18px, line-height 1.5 to 1.7).
- Keep line length between 45 and 75 characters (
max-width: 65chis a good default).
Layout and spacing
- Use a 4/8px spacing scale defined as tokens, and use it everywhere.
- Give sections room to breathe: 80 to 120px vertical padding on desktop, 48 to 64px on mobile.
- Constrain the container to about 1100 to 1200px, and keep reading text narrower.
- Build mobile-first with CSS grid and flexbox. Everything must work from 360px up with no horizontal scrolling; wide tables, code, and diagrams scroll inside their own container.
- Vary the rhythm between sections (density, alignment, scale) instead of repeating one block. Left-align long text.
Surfaces and components
- Use one radius system with two or three sizes, matched to hierarchy (smaller on inputs and buttons, larger on containers).
- Use 1px low-contrast borders and soft, layered shadows with one consistent light direction.
- Give every interactive element hover,
:focus-visible, active, and disabled states. Never remove an outline without replacing it. - Use one primary button per view, labeled with what happens ("Book a class", not "Submit"), with a touch target of at least 44px.
- Give form fields visible labels and put error text next to the field it describes.
Motion
- Use 150 to 250ms ease-out transitions for state changes, so motion shows what changed.
- Prefer one orchestrated moment (a page-load sequence or a hero reveal) over entrance animations on every section.
- Animate only
transformandopacity. - Respect
prefers-reduced-motionby turning off non-essential motion.
Imagery and icons
- Never ship broken or placeholder images. Use the assets provided, inline SVG, or CSS shapes and gradients.
- Keep one icon set with one stroke weight. Write meaningful alt text, and use
alt=""for purely decorative images.
3. Page structure
A common arc: hero (one headline, one primary action), proof (specific numbers, logos, or testimonials), core content (features, work, or pricing), details or FAQ, closing action, footer. Adapt it to the subject and drop sections that have nothing real to say.
Copy
- Write real, specific copy. No lorem ipsum and no "Feature One".
- Write from the visitor's point of view in plain words, sentence case, and active voice.
- Make headlines say what the thing is or does, and keep names for things consistent across the page.
Technical floor
- Use semantic HTML (
header,nav,main,section,footer), a singleh1, and heading levels in order. - Make everything keyboard navigable, add a skip link on long pages, and use ARIA only where native elements fall short.
- Include the viewport meta tag, a title, a description, and a favicon.
- Keep dependencies minimal. A small site can be one self-contained HTML file with inline CSS and JS. In an existing project, follow its stack and conventions instead of introducing new ones.
- Prevent layout shift by setting width and height or
aspect-ratioon media.
Common tells to avoid
These show up on pages built without a point of view:
- Identical rounded cards with the same grey shadow for every piece of content.
- Gradient washes and glowing blobs as decoration.
- A small tracked-out ALL-CAPS label above every heading.
- Numbered markers (01, 02, 03) on content that isn't actually a sequence.
- One word in each headline set in italic or in the accent color.
- Fade-up on every section and a hover lift on every card.
- Everything centered.
Final review
Before presenting the work, check it (with a screenshot or browser if available):
- Spacing and alignment follow the scale, with no stray values.
- Contrast and focus rings pass, and every interactive state exists.
- Layout holds at 360px, tablet, and desktop.
- Nothing is placeholder, broken, or unlabeled.
- Spend boldness in one place: let one element be memorable, keep the rest quiet, and cut any decoration that doesn't serve the subject.