Liam Walker Design System
Liam Walker is a stark, confident one-person portfolio. The page is pure white with near-black type, and the hero is just two words, VISUAL DESIGNER, in Clash Display at 224px filling the screen. Below that, projects run in a zigzag: a big uppercase title that pushes across into the photo beside it, a line of services in grey Inter, and a small VIEW PROJECT link. The one touch of colour is an orange-to-salmon gradient on a single italic word per section title (LATEST *WORK*).
Signatures:
- Poster hero. VISUAL / DESIGNER at 224px, weight 600, line height 0.8, 3px tracking, uppercase, with tiny social icons bottom-left and SCROLL ↓ bottom-right. Nothing else on the first screen.
- Gradient italic word. Section titles are bold roman uppercase with one word in light italic filled with a 45° gradient from #FF4B1F to #FF9068.
- Overlapping project titles. In each project row the title block is pulled 120px into the image column, so the last letters sit on top of the photo (PENDISSE PULVINAR, QUISQUE MALESUADA).
- Black wipe reveals. Headings are revealed by a black block that sweeps across them from left to right.
Colors
Surfaces
#FFFFFFPage background and the nav bar
#FFFFFFSame as canvas: there are no raised panels
#000000Full-screen menu, heading wipe blocks
Ink
#FFFFFFText on primary
#171717Headlines, project titles, field labels (--black)
#000000MENU, VIEW PROJECT, SCROLL, the logo
#2F3330Lead paragraphs at 21px (--dark-slate-grey)
#6E6E6EParagraphs, project service lists, input text (--dim-grey)
#FFFFFF#FFFFFFText on inverse-canvas
Action
#424242The filled .button (Send Message)
#2B2B2BButton hover (measured)
#FF4B1FThe 45° gradient clipped to italic heading words (.italic-text)
#FF9068With accent: The 45° gradient clipped to italic heading words (.italic-text)
#FFCF68End of the 84° orange-to-gold gradient on decorative shapes (#FF4B1F → #FFCF68)
Lines & effects
#DDDDDD1px underline on form fields
Typography
Clash Display · display-hero
The quick brown fox jumpsVISUAL DESIGNER (.title-1, 14rem). 224px · 600 · 0.8 · 3px
Clash Display · headline-menu
The quick brown fox jumpsFull-screen menu links (.navlinks; the CSS asks for 700, but only the 600 face loads). 74px · 600 · 0.81 · 4px
Inter · body-lg
The quick brown fox jumpsLead lines under titles, in ink-lead. 21px · 400 · 1.24
Clash Display · label
The quick brown fox jumpsVIEW PROJECT, SCROLL (.button-line). 12px · 600 · 1.67 · 2px
Clash Display · caption
The quick brown fox jumpsForm field labels. 11px · 600 · 1.82 · 1px
Spacing & shape
| Purpose | Value |
|---|---|
| Container | max 1200px, centred |
| Section intro | a centred title and one body-lg line, then about 200px of space before the first project |
| Breakpoints | 991px, 767px and 479px; project rows stack to one column at ≤767 (a column-reverse flex, so the image sits above the text) |
Spacing scale
| Token | Value | Preview |
|---|---|---|
hair | 5px | |
sm | 16px | |
md | 30px | |
lg | 32px | |
xl | 100px |
Layout spacing
| Token | Value | Preview |
|---|---|---|
section-end | 30px | |
nav-height | 70px | |
section-side | 72px | |
section | 100px | |
overlap | 120px |
Border radius
Motion
| Heading wipe | A black .heading-overlay moves x −100% → 0% (300ms easeIn), then 0% → 100% (300ms easeOut), uncovering the text |
| Mask reveal | Size on masked blocks, 500ms outExpo or ease |
| Slide-in | Opacity 0 → 1 and x −30px → 0, 500ms outExpo |
| Slow reveal | Opacity 0 → 1 and move to 0, 0, 1000ms outQuart |
| Parallax | While scrolling in view: images and shapes move between y 300px and y −300px (and −100px) across the viewport |
| Cursor follow | Mouse move: shapes and images shift slightly with the pointer |
| Text roll | Logo and links move y 0 → −20px, 400ms ease, inside overflow-hidden masks |
| Button hover | transition: all 0.2s |
Do’s and don’ts
- Keep the page white #FFFFFF with #171717 headlines and #6E6E6E Inter paragraphs.
- Set headings in uppercase Clash Display 600 and, in section titles, switch one word to 400 italic with the #FF4B1F → #FF9068 gradient.
- Give the hero only one or two huge words (224px, line height 0.8, 3px tracking).
- Let project titles overlap the image by about 120px and alternate row sides.
- Use 12px uppercase text links with 2px tracking for actions on the home page.
- Reveal headings with a black wipe and masked text.
- Add cards, shadows, borders or rounded images.
- Use the orange gradient as a background, a button fill or on more than one word per heading.
- Put Clash Display on paragraphs or Inter on headings.
- Add filled buttons to the home page; the #424242 button belongs to forms and inner pages.
- Write headings in sentence case or long paragraphs under project titles.
- Let decorative shapes crowd the titles; keep one per row at most.
Example prompt
Any page in the Liam Walker style
More design systems like this
Portfolio design systems, the same colors first.
Bring any of them to your AI tool
All Access unlocks all 398 design systems, ready for Claude, ChatGPT, Gemini, Cursor, v0 and Lovable, plus 400+ templates on all 5 platforms.
Get All AccessUpgrade to All AccessHow to use the Liam Walker design system
Pick a file to see what it’s for and where it goes.
What it is
The whole design system in one markdown file, written for AI: every color, type style, spacing value, component and motion rule, plus do's, don'ts and a ready prompt.
Best for
Claude, ChatGPT, Gemini, Cursor and v0, or any other AI tool that builds pages or code.
How to use it
- Put
DESIGN.mdin your project and mention it in your request, or save it as.cursor/rules/liam.mdc - For the rule file, start it with a front-matter block that sets
alwaysApply: true, so every chat uses it - Ask: “Build a pricing page using DESIGN.md.” Cursor follows the colors, fonts, spacing and rules
- Put
DESIGN.mdin the project root - Add one line to
CLAUDE.md: “Follow DESIGN.md for all UI.” - Ask for any page or component; Claude reads the file first
- Attach
DESIGN.mdto the chat (or paste it in) - Ask: “Build a landing page in this design system.”
- Keep the file in the chat or project knowledge, so follow-up pages stay on style
What it is
Every token as data, in the W3C Design Tokens format: colors with their roles, type styles, radius, spacing, and component tokens that point at them.
Best for
Figma (Tokens Studio), Style Dictionary and other design-token tools, and build scripts.
How to use it
- In Figma, open Tokens Studio, choose Import, and pick
tokens.json - Or point Style Dictionary’s
sourceat it to generate tokens for any platform - In code, import it like any JSON file
What it is
A Tailwind CSS v4 theme: every color, font, type style, radius and spacing value becomes a Tailwind utility, like bg-canvas, text-headline-lg or rounded-md.
Best for
Tailwind v4 projects, and AI builders that write Tailwind (v0, Lovable, Bolt).
How to use it
- Save
theme.cssnext to your main CSS file - Import it after Tailwind:
@import "tailwindcss"; @import "./theme.css"; - Use the classes:
bg-canvas text-ink rounded-md p-lg
What it is
The same tokens as plain CSS variables on :root. Component values point at the color variables, so changing one color updates everything that uses it.
Best for
Any website: plain CSS, Webflow custom code, Framer, WordPress.
How to use it
- Add it to your stylesheet, or in Webflow paste it into Site settings → Custom code inside a
<style>tag - Use the variables anywhere:
color: var(--color-ink) - Change a token once and every place that uses it follows






