Quillhaven

A light, near-monochrome and restrained visual system for a consumer brand store. Its look rests on 500-weight display type up to 32px, monospace used for labels, metadata or code and a monochrome palette on a white canvas. Apply it to a marketing site or the public pages of an app; the tokens and component specs carry the identity.

Build in this styleRead the build prompt

In the builder, open Gallery under the message and search for Quillhaven.

What makes it

• 500-weight display type up to 32px
• monospace used for labels, metadata or code
• short uppercase labels with open tracking
• square corners on controls (0-2px)
• no shadows; depth comes from surface tone steps
• very generous vertical spacing between sections

Colors

Crisp, rational, understated. A white ground, 500-weight display type up to 32px and a monochrome palette set the tone.

• canvas / primary action label#ffffff
• surface#dad9d5
• text / primary action fill / focus ring#030303
• muted text#605e61
• divider (decorative), never behind text#f6eada
• input border#a46f28

Every checked pair, measured again

Typefaces

monospace accents in Roboto Mono; uppercase only for short labels, with at least 0.05em tracking; no text below 12px; weights of 300 or lighter only at 24px and above; fonts are open Google Fonts chosen to match the observed letterforms

• InterHeadings
• InterBody
• Roboto MonoFigures and code

Type scale

Corners and shadows

• cards: 0px
• badges: 0px
• images: 0px
• inputs: 0px
• buttons: 0px

No shadows: depth comes from surfaces and lines.

Spacing and imagery

spacious density on a 4px base unit; container 1440px; section gap 72px; card padding 40px; element gap 12px; radii cards 0px, badges 0px, images 0px, inputs 0px, buttons 0px; no shadows

Photography, product screenshots, illustration, 3d renders. Use placeholder or generated imagery only; partner marks are neutral placeholders in the muted text color. Product views sit in framed panels with the card radius. Photography is shown under a scrim wherever text overlaps it. Icons are outline style at 20-24px in the text or muted color.

Layout

1. thin announcement strip with one inline link and a dismiss button
2. top navigation: wordmark left, 4-6 text links, primary action right; collapses to a menu sheet under 768px
3. centered hero: headline, one-line lede and a primary plus secondary action, visual below
4. article or story cards with image, kicker, title and date
5. large framed product view on a tinted surface
6. alternating two-column text-and-visual blocks
7. row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
8. product grid: image, name, price and quick-add, 4 columns desktop / 2 mobile
9. closing call-to-action band with heading and primary action
10. newsletter sign-up with a labeled email field
11. footer with grouped link columns, legal line and social icons
12. content sits in a 1440px centered container with 24px side padding (16px on mobile)
13. sections are separated by 72px of vertical space on desktop, roughly half that on mobile

Patterns

• thin announcement strip with one inline link and a dismiss button
• hero
• article or story cards with image, kicker, title and date
• large framed product view on a tinted surface
• alternating two-column text-and-visual blocks
• row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
• product grid
• closing call-to-action band with heading and primary action
• newsletter sign-up with a labeled email field

Components

• announcement strip: colors: canvas #ffffff, text #030303; type 12px; uppercase with at least 0.05em tracking
• top navigation bar: colors: canvas #ffffff, text #030303; uppercase with at least 0.05em tracking
• hero block: colors: canvas #ffffff, text #030303; uppercase with at least 0.05em tracking; underlined
• text link: colors: text #030303; uppercase with at least 0.05em tracking; underlined
• primary button: fill #030303, label #ffffff; 1px border; uppercase with at least 0.05em tracking
• content card: colors: canvas #ffffff, text #030303; no shadow; uppercase with at least 0.05em tracking
• product frame: colors: text #030303, canvas #ffffff; uppercase with at least 0.05em tracking
• footer: colors: canvas #ffffff, surface #dad9d5; uppercase with at least 0.05em tracking
• top navigation bar (variant 2): colors: text #030303, canvas #ffffff; uppercase with at least 0.05em tracking
• pill badge: colors: text #030303; uppercase with at least 0.05em tracking
• text input: colors: text #030303; 1px border

Interactions and states

• opacity and color transitions only, 150ms ease-out
• every interactive element shows a 2px #030303 focus ring with 2px offset
• primary action darkens or lightens by one step on hover and keeps its label color
• fields show the focus ring on focus and inline validation on blur
• navigation collapses to a full-height menu sheet under 768px, trapping focus while open
• all motion is disabled under prefers-reduced-motion
• images show a surface-colored placeholder until loaded, with alt text if they fail
• forms: inline validation, disabled submit while sending, success message and retryable error
• mobile menu open and closed states
• hover, focus-visible, active and disabled states for every button style
• reduced-motion variant with no transitions beyond opacity
• out-of-stock product tile with a disabled add button and 'Notify me' alternative
• cart count badge updates after add

Guardrails

Experience

• Keep one primary action style (#030303 fill, #ffffff label) and use it once per view; secondary actions stay outlined or text-only.
• Keep corners square on every control; do not mix in rounded or pill shapes.
• Limit headline sizes to the type scale; the 32px display size appears once per page, in the hero.
• Separate layers with surface tone and hairlines, not shadows.
• Partner and customer marks are placeholders in one muted tone; never use real company logos.
• Keep copy short and concrete: one idea per section, with a heading that states the benefit.

Accessibility

• Text, links, focus rings and input borders use only the verified pairs listed in contrast checks.
• Focus ring: 2px solid #030303 with 2px offset on every interactive element.
• Body text is 16px or larger at 1.5 line height; nothing is smaller than 12px.
• Decorative colors (dividers and supporting accents) never carry text or the only signal of state.
• Uppercase labels stay short, use at least 0.05em tracking and keep sentence-case text in the HTML source.
• Text over photos or gradients sits on a scrim that keeps it at 4.5:1 against the lightest area.
• Respect prefers-reduced-motion; no parallax or autoplay video without a pause control.
• Some observed colors were moved to the nearest passing shade of the same hue; use the palette values here, not lighter originals.

Security

• Validate every form with a shared zod schema on the client and again in the edge function; reject unknown fields.
• Rate-limit form endpoints per IP and add a honeypot field; store leads in a Supabase table with RLS allowing insert only for anonymous users and select only for staff.
• Set a strict Content-Security-Policy, self-host fonts and icons, and avoid third-party scripts beyond privacy-friendly analytics.
• Open external links with rel="noopener noreferrer" and never put secrets or API keys in client code.
• Checkout goes through a hosted payment provider; the site never handles card data, and prices are re-validated on the server.

Build prompt

The rules every style in the gallery assumes, then this style’s own ten sections, from goal to guardrails. A build in the style also gets its tokens as a file, so the colors and type above are exact.

Copy the rules and build prompt

### How to use these prompts
Paste an entry's build prompt into your coding agent as the first message. Each prompt names its own stack, tokens and acceptance criteria; the rules below apply to all of them and can be prepended once per project.

### Engineering baseline
- TypeScript strict mode, no `any`, small typed components, feature folders, and one source of truth for design tokens (CSS variables consumed by Tailwind).
- Validate every input with a shared zod schema on the client and again on the server or edge function. Never trust client-side checks alone.
- Show loading, empty and error states for every async view. Surface errors in plain language with a retry, and log details to the console in development only.
- Keep secrets out of the bundle. Only publishable keys (for example a Supabase anon key) belong in client code; service-role keys, API keys and webhooks live in server or edge-function environment variables.

### Data and auth baseline
- Enable Row Level Security on every table before inserting data. Default-deny, then add the narrowest policies the feature needs (for a lead form: insert-only for anonymous users, select for a staff role).
- Store roles in a separate table checked by a security-definer function, never in a user-editable profile field.
- Rate-limit public endpoints (forms, auth, AI calls) and add a honeypot field or captcha to anonymous forms.
- Take payments through a hosted checkout and verify webhooks by signature. Never handle raw card data.

### Accessibility and UX baseline
- Target WCAG 2.2 AA: 4.5:1 contrast for normal text and 3:1 for large text, input borders, focus rings and meaningful icons or chart lines. Every palette in this catalog lists its verified pairs; re-check with a contrast tool after any color change.
- Keep body text at 16px or larger with 1.5 line height, nothing below 12px, no light weights under 24px, and uppercase only for short labels.
- Give every interactive element a visible focus ring, full keyboard support, semantic landmarks, labeled form fields, and alt text on meaningful images.
- Respect `prefers-reduced-motion` for every animation. Give carousels and drag interactions keyboard and button alternatives, and never auto-advance them.
- Build mobile-first and test at 375px, 768px and 1280px.

### Content guardrails
- Use original copy, fictional sample data and placeholder or generated imagery. Do not reuse another product's name, logo, screenshots or marketing text.
- Partner and customer logo rows use neutral placeholder marks. Label demo testimonials and metrics as samples. Collect the minimum personal data a form needs.

### Style preset baseline
- Treat the entry's palette, type scale, radii, spacing and shadows as the complete token set. Do not introduce new colors; derive hover and pressed states by moving one step lighter or darker within the same hue, then re-check contrast.
- Colors marked decorative (dividers, supporting accents) never sit behind text and never carry meaning on their own.
- Fonts are open Google Fonts chosen to match the observed letterforms. Self-host them with `font-display: swap` and keep to the listed weights.
- Keep the signature moves listed for the entry, and keep everything else quiet so they stay recognizable.
- One primary action style per view. Secondary actions are outlined or text-only, and links are distinguishable by more than color (underline or weight).

### Goal
Build a responsive light-theme marketing site for a fictional consumer brand store in the "Quillhaven" style: near-monochrome and restrained, with 500-weight display type up to 32px, monospace used for labels, metadata or code, short uppercase labels with open tracking. Use invented copy and placeholder imagery throughout.

### Stack
React 18 + Vite, TypeScript, Tailwind CSS, shadcn/ui (Radix), lucide-react, TanStack Query, zod, Supabase (form submissions only). Design tokens live as CSS variables and are mapped into the Tailwind theme.

### Pages & layout
Home page sections, in order:
- thin announcement strip with one inline link and a dismiss button
- top navigation: wordmark left, 4-6 text links, primary action right; collapses to a menu sheet under 768px
- centered hero: headline, one-line lede and a primary plus secondary action, visual below
- article or story cards with image, kicker, title and date
- large framed product view on a tinted surface
- alternating two-column text-and-visual blocks
- row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
- product grid: image, name, price and quick-add, 4 columns desktop / 2 mobile
- closing call-to-action band with heading and primary action
- newsletter sign-up with a labeled email field
- footer with grouped link columns, legal line and social icons
- content sits in a 1440px centered container with 24px side padding (16px on mobile)
- sections are separated by 72px of vertical space on desktop, roughly half that on mobile
Also build a simple contact page with a lead form and a 404 page in the same style. Test at 375px, 768px and 1280px.

### Design system
```css
:root {
  --color-canvas: #ffffff;
  --color-surface: #dad9d5;
  --color-text: #030303;
  --color-muted-text: #605e61;
  --color-divider: #f6eada;
  --color-input-border: #a46f28;
  --text-12: 12px;
  --text-15: 15px;
  --text-16: 16px;
  --text-18: 18px;
  --text-20: 20px;
  --text-28: 28px;
  --text-32: 32px;
  --radius-cards: 0px;
  --radius-badges: 0px;
  --radius-images: 0px;
  --radius-inputs: 0px;
  --radius-buttons: 0px;
  --space-unit: 4px;
  --container: 1440px;
}
```
Display Inter, body Inter, mono Roboto Mono (Google Fonts, self-hosted, font-display: swap).
Type scale (size/weight/line-height tracking): 12px/400/1.15 0.030em, 15px/400/1.45 0.010em, 16px/400/1.5, 18px/400/1.5, 20px/400/1.5, 28px/400/0.92 -0.020em, 32px/500/1.2.
Spacing: spacious density on a 4px base unit; container 1440px; section gap 72px; card padding 40px; element gap 12px; radii cards 0px, badges 0px, images 0px, inputs 0px, buttons 0px; no shadows.
Signature moves: 500-weight display type up to 32px; monospace used for labels, metadata or code; short uppercase labels with open tracking; square corners on controls (0-2px); no shadows; depth comes from surface tone steps; very generous vertical spacing between sections.

### Components & interactions
- **announcement strip**: colors: canvas #ffffff, text #030303; type 12px; uppercase with at least 0.05em tracking
- **top navigation bar**: colors: canvas #ffffff, text #030303; uppercase with at least 0.05em tracking
- **hero block**: colors: canvas #ffffff, text #030303; uppercase with at least 0.05em tracking; underlined
- **text link**: colors: text #030303; uppercase with at least 0.05em tracking; underlined
- **primary button**: fill #030303, label #ffffff; 1px border; uppercase with at least 0.05em tracking
- **content card**: colors: canvas #ffffff, text #030303; no shadow; uppercase with at least 0.05em tracking
- **product frame**: colors: text #030303, canvas #ffffff; uppercase with at least 0.05em tracking
- **footer**: colors: canvas #ffffff, surface #dad9d5; uppercase with at least 0.05em tracking
- **top navigation bar (variant 2)**: colors: text #030303, canvas #ffffff; uppercase with at least 0.05em tracking
- **pill badge**: colors: text #030303; uppercase with at least 0.05em tracking
- **text input**: colors: text #030303; 1px border
- opacity and color transitions only, 150ms ease-out
- every interactive element shows a 2px #030303 focus ring with 2px offset
- primary action darkens or lightens by one step on hover and keeps its label color
- fields show the focus ring on focus and inline validation on blur
- navigation collapses to a full-height menu sheet under 768px, trapping focus while open
- all motion is disabled under prefers-reduced-motion

### Data & state
Content comes from typed local collections: Feature{icon, title, body}, Post{slug, title, kicker, excerpt, coverUrl, publishedAt}, Product{slug, name, price, imageUrl, alt, inStock, swatches[]}, PartnerMark{label, placeholderSvg}, Lead{email, name?, message?, createdAt}. The lead form posts to a Supabase edge function. Handle these states:
- images show a surface-colored placeholder until loaded, with alt text if they fail
- forms: inline validation, disabled submit while sending, success message and retryable error
- mobile menu open and closed states
- hover, focus-visible, active and disabled states for every button style
- reduced-motion variant with no transitions beyond opacity
- out-of-stock product tile with a disabled add button and 'Notify me' alternative
- cart count badge updates after add

### Accessibility
- Text, links, focus rings and input borders use only the verified pairs listed in contrast checks.
- Focus ring: 2px solid #030303 with 2px offset on every interactive element.
- Body text is 16px or larger at 1.5 line height; nothing is smaller than 12px.
- Decorative colors (dividers and supporting accents) never carry text or the only signal of state.
- Uppercase labels stay short, use at least 0.05em tracking and keep sentence-case text in the HTML source.
- Text over photos or gradients sits on a scrim that keeps it at 4.5:1 against the lightest area.
- Respect prefers-reduced-motion; no parallax or autoplay video without a pause control.
- Some observed colors were moved to the nearest passing shade of the same hue; use the palette values here, not lighter originals.
Verified contrast: body text on canvas #030303 on #ffffff = 20.62:1; body text on surface #030303 on #dad9d5 = 14.6:1; muted text on canvas #605e61 on #ffffff = 6.42:1; muted text on surface #605e61 on #dad9d5 = 4.55:1; primary action label on fill #ffffff on #030303 = 20.62:1; focus ring on canvas #030303 on #ffffff = 20.62:1; focus ring on surface #030303 on #dad9d5 = 14.6:1; input border on canvas #a46f28 on #ffffff = 4.3:1.

### Security
- Validate every form with a shared zod schema on the client and again in the edge function; reject unknown fields.
- Rate-limit form endpoints per IP and add a honeypot field; store leads in a Supabase table with RLS allowing insert only for anonymous users and select only for staff.
- Set a strict Content-Security-Policy, self-host fonts and icons, and avoid third-party scripts beyond privacy-friendly analytics.
- Open external links with rel="noopener noreferrer" and never put secrets or API keys in client code.
- Checkout goes through a hosted payment provider; the site never handles card data, and prices are re-validated on the server.

### Performance & SEO
- Static generation for every content page; ship no JavaScript to sections that do not need it.
- Images in AVIF/WebP with explicit width and height, lazy-loaded below the fold; preload the hero image and the display font only.
- One h1 per page, descriptive titles and meta descriptions, Open Graph tags with a generated preview image, and a sitemap.
- Target Lighthouse 95+ for performance, accessibility, best practices and SEO.

### Guardrails
- Keep one primary action style (#030303 fill, #ffffff label) and use it once per view; secondary actions stay outlined or text-only.
- Keep corners square on every control; do not mix in rounded or pill shapes.
- Limit headline sizes to the type scale; the 32px display size appears once per page, in the hero.
- Separate layers with surface tone and hairlines, not shadows.
- Partner and customer marks are placeholders in one muted tone; never use real company logos.
- Keep copy short and concrete: one idea per section, with a heading that states the benefit.
Acceptance criteria:
- Every color in the build comes from the tokens above and every text pair matches a verified contrast pair.
- The page works with keyboard only, shows a visible focus ring everywhere and passes an automated axe check with no violations.
- No real brand names, logos, product screenshots or copied marketing text appear anywhere.
- Layout holds at 375px with no horizontal scrolling.

Open the builderThe whole gallery