Design Fundamentals
A reference for the durable fundamentals of visual design — the principles that
hold across brands, tools, and trends. Use it to make deliberate choices and to
explain them. Good design usually isn't the product of one bold move; it's many
small, consistent decisions about type, space, color, and alignment that add up
to something that feels effortless.
The guiding instinct throughout: reduce noise so the message comes through.
Most visual problems are too much (clutter, too many fonts/colors/sizes,
competing focal points) rather than too little. When something looks wrong but
you can't name why, suspect inconsistency, weak hierarchy, or cramped spacing
first.
This file covers the essentials inline. For a decision, jump to the relevant
section; for a critique, walk all of them.
Typography
Type is most of the design in most interfaces and documents. Get it right and
the rest gets easier.
Readability first.
- Measure (line length): aim for roughly 45–75 characters per line for body
text. Too long and the eye loses its place returning to the next line; too
short and rhythm breaks.
- Line height (leading): body text usually wants ~1.4–1.6× the font size.
Denser for short labels, looser for long-form reading. Larger headings need
tighter relative leading than body.
- Size: body text should be comfortable at its viewing distance — on screen,
~16px and up for primary reading text. Don't make people work.
- Contrast: dark-enough text on its background (see color/accessibility).
Grey-on-grey looks elegant in a mockup and fails in sunlight.
Choosing and pairing typefaces.
- Fewer is better. One well-chosen family with a range of weights carries most
work. If pairing, two is plenty — commonly one for headings, one for body.
- Pair by contrast, not by near-sameness. Two similar sans-serifs clash
subtly; a clear contrast (e.g. a distinctive display face for headings + a
neutral, highly legible face for body) reads as intentional. Superfamilies
(a serif and sans designed together) pair safely.
- Pick faces built for the job: text faces for reading, display faces for
large sizes only. A display face set at 14px is illegible; a text face set
huge looks bland.
Setting type well.
- Establish a type scale — a small set of sizes with clear steps (e.g. a
consistent ratio) rather than arbitrary values. Constraint creates harmony.
- Use weight, size, and color to signal importance, not decoration. Avoid
ALL-CAPS for long strings, underlines for non-links, and italics for whole
paragraphs.
- Mind the details that separate amateur from professional: real punctuation
(curly quotes, en/em dashes), consistent spacing, no rivers of whitespace, no
widows/orphans in important text, and left-aligned body text for most Latin
reading (justified only with good hyphenation).
Color
Color carries meaning, mood, and hierarchy — and is where beginners most often
overreach.
Build a restrained palette.
- Start with a small system: one or two primary colors, a neutral range
(the greys/off-whites that do most of the actual work), and a few accent
colors used sparingly for emphasis and calls to action.
- Reserve your most saturated / attention-grabbing color for the thing you most
want people to notice. If everything is loud, nothing is.
- Use semantic colors consistently (e.g. the same red for errors/destructive
actions, the same green for success) so color becomes a reliable signal.
Make it work technically.
- Think in terms of hue, saturation, and lightness — adjusting lightness and
saturation gives you a coherent family from a single hue. Flat, evenly-spaced
tints/shades look more deliberate than hand-picked colors.
- Contrast is not optional. Text and meaningful UI must meet accessibility
contrast (commonly WCAG AA: ~4.5:1 for normal text, ~3:1 for large text and UI
components). Check it; don't eyeball it.
- Never rely on color alone to convey information — pair it with text, icon,
or shape, so colorblind users and grayscale contexts still work.
- Test the palette in both light and dark contexts if the product supports them.
Layout & grids
Layout is about relationships in space: what's grouped, what's separate, what
leads the eye.
Grids create order.
- A grid (columns, gutters, margins) gives you consistent places to put
things, so alignment happens by default and the design feels stable. Even a
simple grid beats free placement.
- Align intentionally. Every element should line up with something. Strong,
shared edges (a consistent left margin, aligned baselines) read as calm and
professional; stray misalignments read as sloppy even when the viewer can't say
why.
- Choose a column structure to fit the content (e.g. a flexible multi-column grid
for rich layouts, a single strong column for reading).
Space is a material, not leftover.
- Whitespace (negative space) is an active tool. Generous space around an
element gives it importance and makes a layout breathe; crowding signals "less
important" and creates stress. Don't fill every gap.
- Use consistent spacing steps (a spacing scale) rather than arbitrary
margins — 4/8-based systems are common — so rhythm stays even.
- Proximity groups meaning: things close together are read as related; space
between them signals separation. Control grouping with distance before reaching
for boxes and lines.
Composition.
- Give the layout a clear focal point and a path for the eye to follow.
- Balance the composition — symmetry reads as stable/formal; deliberate asymmetry
reads as dynamic — but avoid accidental lopsidedness.
- Respect margins; content that crowds the edges feels tense and can get clipped.
Visual hierarchy & perception
Hierarchy is how you tell the viewer what to look at, in what order. It's arguably
the single most important skill, because a design with perfect type and color but
no hierarchy still fails.
Establish hierarchy with contrast. The eye goes to whatever differs most from
its surroundings. Create order by varying:
- Size (bigger = more important), weight/boldness, color/contrast,
position (top and left-leading spots get seen first in Latin reading), and
space (isolation draws attention).
- Aim for an obvious first thing, second thing, third thing. If two elements
compete for "most important," pick one and demote the other.
Perception principles (Gestalt). People automatically organize what they see;
design with these tendencies, not against them:
- Proximity: near things are seen as a group.
- Similarity: things that look alike are seen as related.
- Common region / enclosure: a shared background or border groups items.
- Continuity & alignment: the eye follows lines and aligned edges.
- Closure: people mentally complete familiar shapes, so you can imply rather
than draw everything.
- Figure/ground: ensure it's clear what's foreground and what's background.
A few broadly useful principles. These recur across good design:
- Consistency — repeating patterns, styles, and components reduces the effort
of understanding and builds trust.
- Signifiers & affordances — make interactive things look interactive and
obvious what they do; don't make people guess.
- Feedback — every action should produce a visible response.
- Progressive disclosure — show what's needed now; reveal complexity on
demand rather than all at once.
- Fitts's law — important/ frequent targets should be bigger and easier to
reach; Hick's law — more choices means slower decisions, so curate.
- Aesthetic-usability effect — people perceive attractive designs as easier to
use, which is why polish is functional, not vanity.
How to use this in a critique
When giving design feedback, go in order of impact rather than nitpicking:
- Hierarchy — is it instantly clear what matters most? What to do first?
- Layout & alignment — is everything aligned to something; is spacing
consistent; does it breathe?
- Typography — is it readable; is the type system restrained and consistent?
- Color — is the palette restrained, purposeful, accessible?
- Consistency & detail — repeated patterns, real punctuation, polish.
Explain the why behind each note (tie it to a principle above), and lead with
the changes that will improve the piece most. One structural fix (establish
hierarchy, align to a grid) usually beats ten cosmetic tweaks.
Further reading
If the user wants to go deeper, these are widely-respected texts on the topics
above (recommend by title/author; this skill does not reproduce their contents):
Thinking with Type (Ellen Lupton) for typography; Grid Systems in Graphic
Design (Josef Müller-Brockmann) for grids; Universal Principles of Design
(Lidwell, Holden, Butler) for a broad principle catalog; The Elements of User
Experience (Jesse James Garrett) for how visual design sits within UX; and
foundational writing on color systems for palette theory.
Bundled tools
scripts/scales.py — generate an exact modular type scale
(type --base 16 --ratio 1.25) and a color tint/shade ramp with per-stop
WCAG contrast against white and black (color --base "#2456E0" --steps 9). Use
it so the scale is reproducible rather than hand-rounded, and so palette stops
come with their contrast already computed.
Pairs well with
- heuristic-evaluation / accessibility-review — the fundamentals here underlie many findings in both.
- inclusive-design — pair visual clarity with inclusive, equitable choices.
Sources
The books listed above are cited as further reading only. This reference
states general, field-wide principles in its own words and does not reproduce
their text or figures — so don't paste copyrighted passages from those works into
outputs; cite them and paraphrase.
1---2name: design-fundamentals3description: A working reference for visual and graphic design fundamentals — typography, color, layout and grids, visual hierarchy, spacing, and the perception principles behind them. Consult this whenever making or critiquing visual design decisions: choosing or pairing typefaces, setting type for readability, building a color palette, laying out a page/screen/slide/poster, establishing hierarchy, fixing a cluttered or unbalanced composition, or explaining *why* a design does or doesn't work. Use it when the user asks for design feedback, wants their layout/typography/color improved, or is designing any visual artifact and wants it to look considered rather than accidental. Reach for this even when "design fundamentals" isn't named — any real visual-design choice benefits from it.4---56# Design Fundamentals78A reference for the durable fundamentals of visual design — the principles that9hold across brands, tools, and trends. Use it to make deliberate choices and to10explain them. Good design usually isn't the product of one bold move; it's many11small, consistent decisions about type, space, color, and alignment that add up12to something that feels effortless.1314The guiding instinct throughout: **reduce noise so the message comes through.**15Most visual problems are too much (clutter, too many fonts/colors/sizes,16competing focal points) rather than too little. When something looks wrong but17you can't name why, suspect inconsistency, weak hierarchy, or cramped spacing18first.1920This file covers the essentials inline. For a decision, jump to the relevant21section; for a critique, walk all of them.2223## Typography2425Type is most of the design in most interfaces and documents. Get it right and26the rest gets easier.2728**Readability first.**29- **Measure (line length):** aim for roughly 45–75 characters per line for body30 text. Too long and the eye loses its place returning to the next line; too31 short and rhythm breaks.32- **Line height (leading):** body text usually wants ~1.4–1.6× the font size.33 Denser for short labels, looser for long-form reading. Larger headings need34 *tighter* relative leading than body.35- **Size:** body text should be comfortable at its viewing distance — on screen,36 ~16px and up for primary reading text. Don't make people work.37- **Contrast:** dark-enough text on its background (see color/accessibility).38 Grey-on-grey looks elegant in a mockup and fails in sunlight.3940**Choosing and pairing typefaces.**41- **Fewer is better.** One well-chosen family with a range of weights carries most42 work. If pairing, two is plenty — commonly one for headings, one for body.43- **Pair by contrast, not by near-sameness.** Two similar sans-serifs clash44 subtly; a clear contrast (e.g. a distinctive display face for headings + a45 neutral, highly legible face for body) reads as intentional. Superfamilies46 (a serif and sans designed together) pair safely.47- **Pick faces built for the job:** text faces for reading, display faces for48 large sizes only. A display face set at 14px is illegible; a text face set49 huge looks bland.5051**Setting type well.**52- Establish a **type scale** — a small set of sizes with clear steps (e.g. a53 consistent ratio) rather than arbitrary values. Constraint creates harmony.54- Use **weight, size, and color** to signal importance, not decoration. Avoid55 ALL-CAPS for long strings, underlines for non-links, and italics for whole56 paragraphs.57- Mind the details that separate amateur from professional: real punctuation58 (curly quotes, en/em dashes), consistent spacing, no rivers of whitespace, no59 widows/orphans in important text, and left-aligned body text for most Latin60 reading (justified only with good hyphenation).6162## Color6364Color carries meaning, mood, and hierarchy — and is where beginners most often65overreach.6667**Build a restrained palette.**68- Start with a small system: one or two **primary** colors, a **neutral** range69 (the greys/off-whites that do most of the actual work), and a few **accent**70 colors used sparingly for emphasis and calls to action.71- Reserve your most saturated / attention-grabbing color for the thing you most72 want people to notice. If everything is loud, nothing is.73- Use **semantic** colors consistently (e.g. the same red for errors/destructive74 actions, the same green for success) so color becomes a reliable signal.7576**Make it work technically.**77- Think in terms of hue, saturation, and lightness — adjusting lightness and78 saturation gives you a coherent family from a single hue. Flat, evenly-spaced79 tints/shades look more deliberate than hand-picked colors.80- **Contrast is not optional.** Text and meaningful UI must meet accessibility81 contrast (commonly WCAG AA: ~4.5:1 for normal text, ~3:1 for large text and UI82 components). Check it; don't eyeball it.83- **Never rely on color alone** to convey information — pair it with text, icon,84 or shape, so colorblind users and grayscale contexts still work.85- Test the palette in both light and dark contexts if the product supports them.8687## Layout & grids8889Layout is about relationships in space: what's grouped, what's separate, what90leads the eye.9192**Grids create order.**93- A **grid** (columns, gutters, margins) gives you consistent places to put94 things, so alignment happens by default and the design feels stable. Even a95 simple grid beats free placement.96- **Align intentionally.** Every element should line up with something. Strong,97 shared edges (a consistent left margin, aligned baselines) read as calm and98 professional; stray misalignments read as sloppy even when the viewer can't say99 why.100- Choose a column structure to fit the content (e.g. a flexible multi-column grid101 for rich layouts, a single strong column for reading).102103**Space is a material, not leftover.**104- **Whitespace** (negative space) is an active tool. Generous space around an105 element gives it importance and makes a layout breathe; crowding signals "less106 important" and creates stress. Don't fill every gap.107- Use **consistent spacing steps** (a spacing scale) rather than arbitrary108 margins — 4/8-based systems are common — so rhythm stays even.109- **Proximity groups meaning:** things close together are read as related; space110 between them signals separation. Control grouping with distance before reaching111 for boxes and lines.112113**Composition.**114- Give the layout a clear **focal point** and a path for the eye to follow.115- Balance the composition — symmetry reads as stable/formal; deliberate asymmetry116 reads as dynamic — but avoid accidental lopsidedness.117- Respect margins; content that crowds the edges feels tense and can get clipped.118119## Visual hierarchy & perception120121Hierarchy is how you tell the viewer what to look at, in what order. It's arguably122the single most important skill, because a design with perfect type and color but123no hierarchy still fails.124125**Establish hierarchy with contrast.** The eye goes to whatever differs most from126its surroundings. Create order by varying:127- **Size** (bigger = more important), **weight/boldness**, **color/contrast**,128 **position** (top and left-leading spots get seen first in Latin reading), and129 **space** (isolation draws attention).130- Aim for an obvious first thing, second thing, third thing. If two elements131 compete for "most important," pick one and demote the other.132133**Perception principles (Gestalt).** People automatically organize what they see;134design with these tendencies, not against them:135- **Proximity:** near things are seen as a group.136- **Similarity:** things that look alike are seen as related.137- **Common region / enclosure:** a shared background or border groups items.138- **Continuity & alignment:** the eye follows lines and aligned edges.139- **Closure:** people mentally complete familiar shapes, so you can imply rather140 than draw everything.141- **Figure/ground:** ensure it's clear what's foreground and what's background.142143**A few broadly useful principles.** These recur across good design:144- **Consistency** — repeating patterns, styles, and components reduces the effort145 of understanding and builds trust.146- **Signifiers & affordances** — make interactive things look interactive and147 obvious what they do; don't make people guess.148- **Feedback** — every action should produce a visible response.149- **Progressive disclosure** — show what's needed now; reveal complexity on150 demand rather than all at once.151- **Fitts's law** — important/ frequent targets should be bigger and easier to152 reach; **Hick's law** — more choices means slower decisions, so curate.153- **Aesthetic-usability effect** — people perceive attractive designs as easier to154 use, which is why polish is functional, not vanity.155156## How to use this in a critique157158When giving design feedback, go in order of impact rather than nitpicking:1591. **Hierarchy** — is it instantly clear what matters most? What to do first?1602. **Layout & alignment** — is everything aligned to something; is spacing161 consistent; does it breathe?1623. **Typography** — is it readable; is the type system restrained and consistent?1634. **Color** — is the palette restrained, purposeful, accessible?1645. **Consistency & detail** — repeated patterns, real punctuation, polish.165166Explain the *why* behind each note (tie it to a principle above), and lead with167the changes that will improve the piece most. One structural fix (establish168hierarchy, align to a grid) usually beats ten cosmetic tweaks.169170## Further reading171172If the user wants to go deeper, these are widely-respected texts on the topics173above (recommend by title/author; this skill does not reproduce their contents):174*Thinking with Type* (Ellen Lupton) for typography; *Grid Systems in Graphic175Design* (Josef Müller-Brockmann) for grids; *Universal Principles of Design*176(Lidwell, Holden, Butler) for a broad principle catalog; *The Elements of User177Experience* (Jesse James Garrett) for how visual design sits within UX; and178foundational writing on color systems for palette theory.179180## Bundled tools181182- `scripts/scales.py` — generate an exact modular **type scale**183 (`type --base 16 --ratio 1.25`) and a **color tint/shade ramp** with per-stop184 WCAG contrast against white and black (`color --base "#2456E0" --steps 9`). Use185 it so the scale is reproducible rather than hand-rounded, and so palette stops186 come with their contrast already computed.187188## Pairs well with189190- **heuristic-evaluation** / **accessibility-review** — the fundamentals here underlie many findings in both.191- **inclusive-design** — pair visual clarity with inclusive, equitable choices.192193## Sources194195The books listed above are cited as **further reading only**. This reference196states general, field-wide principles in its own words and does not reproduce197their text or figures — so don't paste copyrighted passages from those works into198outputs; cite them and paraphrase.