Skip to main content
vibld

Style gallery

Larkstow

Monochrome minimal online store site on white with a sparing blue accent

Light · Monochrome minimal · E-commerce · front-end app (local state)

A near-monochrome and restrained light-theme style for a consumer brand store website. Its look rests on heavy 700-weight display type up to 128px, tight display tracking (-0.040em) and a sparing blue accent 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 Larkstow.

What makes it

  • heavy 700-weight display type up to 128px
  • tight display tracking (-0.040em)
  • monospace used for labels, metadata or code
  • short uppercase labels with open tracking
  • rounded 10px controls
  • no shadows; depth comes from surface tone steps
  • one blue accent used sparingly
  • contrasting full-width bands to break the page rhythm

Colors

Crisp, rational, understated. The white canvas and tight display tracking (-0.040em) carry most of the character.

  • canvas / primary action label / text on band#ffffff
  • surface#ecedee
  • text#111111
  • muted text#676b73
  • divider (decorative), never behind text#a1a4aa
  • input border#84878f
  • accent / primary action fill / link text / focus ring#000aff
  • inverse band#3b3b3b

Every checked pair, measured again

SampleWhereRatioNeeds
Aabody text on canvas18.88:14.5:1
Aabody text on surface16.11:14.5:1
Aamuted text on canvas5.35:14.5:1
Aamuted text on surface4.56:14.5:1
Aaprimary action label on fill8.44:14.5:1
Aalink text on canvas8.44:14.5:1
focus ring on canvas8.44:13:1
focus ring on surface7.20:13:1
input border on canvas3.59:13:1
accent icons and active marks on canvas8.44:13:1
Aatext on inverse band11.20:14.5:1

Typefaces

monospace accents in Space 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
  • Space MonoFigures and code

Type scale

128px Inter 700

64px Inter 700

40px Inter 700

32px Inter 700

20px Inter 400

16px Inter 400

13px Inter 400

Corners and shadows

  • cards: 10px
  • pills: 30px
  • badges: 30px
  • images: 10px
  • inputs: 10px
  • buttons: 10px

No shadows: depth comes from surfaces and lines.

Spacing and imagery

comfortable density on a 4px base unit; container 1440px; section gap 80px; card padding 20px; element gap 16px; radii cards 10px, pills 30px, badges 30px, images 10px, inputs 10px, buttons 10px; no shadows

Photography, product screenshots, illustration, line icons. 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; translucent with backdrop blur and a solid fallback
  3. full-bleed hero with media behind a scrim and the headline anchored lower left
  4. feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
  5. tabbed showcase that swaps a panel per tab
  6. article or story cards with image, kicker, title and date
  7. large framed product view on a tinted surface
  8. row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
  9. product grid: image, name, price and quick-add, 4 columns desktop / 2 mobile
  10. metrics band with three or four large figures and captions
  11. horizontal card rail with previous/next buttons and snap scrolling
  12. footer with grouped link columns, legal line and social icons
  13. content sits in a 1440px centered container with 24px side padding (16px on mobile)
  14. sections are separated by 80px of vertical space on desktop, roughly half that on mobile

Patterns

  • thin announcement strip with one inline link and a dismiss button
  • hero
  • feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
  • tabbed showcase that swaps a panel per tab
  • article or story cards with image, kicker, title and date
  • large framed product view on a tinted surface
  • row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
  • product grid
  • metrics band with three or four large figures and captions
  • horizontal card rail with previous/next buttons and snap scrolling

Components

  • primary button: fill #000aff, label #ffffff; 10px radius
  • announcement strip: colors: text #111111, canvas #ffffff; type 13px
  • top navigation bar: colors: canvas #ffffff, text #111111, muted text #676b73; 10px radius; padding 8px 14px
  • hero block: colors: canvas #ffffff
  • content card: colors: canvas #ffffff, muted text #676b73, text #111111; 20px radius; padding 8px 20px; type 12px
  • content card (variant 2): colors: surface #ecedee, canvas #ffffff, muted text #676b73; 10px radius; type 12px; translucent backdrop with blur (solid fallback)
  • pill badge: colors: accent #000aff, canvas #ffffff; 30px radius; padding 4px 8px
  • pill badge (variant 2): colors: divider (decorative) #a1a4aa, canvas #ffffff; 30px radius; padding 4px 8px
  • secondary button: fill canvas #ffffff; label text #111111; 10px radius; padding 12px 24px; 1px border
  • feature card: colors: text #111111, muted text #676b73, canvas #ffffff; type 12px
  • top navigation bar (variant 2): colors: surface #ecedee, muted text #676b73; 10px radius; 1px border
  • logo row: colors: canvas #ffffff, surface #ecedee; 6px radius; 1px border

Interactions and states

  • opacity and color transitions only, 150ms ease-out
  • every interactive element shows a 2px #000aff focus ring with 2px offset
  • primary action darkens or lightens by one step on hover and keeps its label color
  • 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 (#000aff fill, #ffffff label) and use it once per view; secondary actions stay outlined or text-only.
  • Use the blue accent for small marks only (links, active states, icons), at most two or three times per screen.
  • Keep the 10px control radius consistent across buttons, inputs and chips.
  • Limit headline sizes to the type scale; the 128px 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 #000aff 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.

The rules every style assumes
### 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 "Larkstow" style: near-monochrome and restrained, with heavy 700-weight display type up to 128px, tight display tracking (-0.040em), monospace used for labels, metadata or code. 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; translucent with backdrop blur and a solid fallback
- full-bleed hero with media behind a scrim and the headline anchored lower left
- feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
- tabbed showcase that swaps a panel per tab
- article or story cards with image, kicker, title and date
- large framed product view on a tinted surface
- 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
- metrics band with three or four large figures and captions
- horizontal card rail with previous/next buttons and snap scrolling
- 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 80px 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: #ecedee;
  --color-text: #111111;
  --color-muted-text: #676b73;
  --color-divider: #a1a4aa;
  --color-input-border: #84878f;
  --color-accent: #000aff;
  --color-inverse-band: #3b3b3b;
  --text-13: 13px;
  --text-16: 16px;
  --text-20: 20px;
  --text-32: 32px;
  --text-40: 40px;
  --text-64: 64px;
  --text-128: 128px;
  --radius-cards: 10px;
  --radius-pills: 30px;
  --radius-badges: 30px;
  --radius-images: 10px;
  --radius-inputs: 10px;
  --radius-buttons: 10px;
  --space-unit: 4px;
  --container: 1440px;
}
```
Display Inter, body Inter, mono Space Mono (Google Fonts, self-hosted, font-display: swap).
Type scale (size/weight/line-height tracking): 13px/400/1.4, 16px/400/1.4, 20px/400/1.5 -0.040em, 32px/700/1.2 -0.040em, 40px/700/1.15 -0.040em, 64px/700/1.0 -0.040em, 128px/700/1.0 -0.040em.
Spacing: comfortable density on a 4px base unit; container 1440px; section gap 80px; card padding 20px; element gap 16px; radii cards 10px, pills 30px, badges 30px, images 10px, inputs 10px, buttons 10px; no shadows.
Signature moves: heavy 700-weight display type up to 128px; tight display tracking (-0.040em); monospace used for labels, metadata or code; short uppercase labels with open tracking; rounded 10px controls; no shadows; depth comes from surface tone steps; one blue accent used sparingly; contrasting full-width bands to break the page rhythm.

### Components & interactions
- **primary button**: fill #000aff, label #ffffff; 10px radius
- **announcement strip**: colors: text #111111, canvas #ffffff; type 13px
- **top navigation bar**: colors: canvas #ffffff, text #111111, muted text #676b73; 10px radius; padding 8px 14px
- **hero block**: colors: canvas #ffffff
- **content card**: colors: canvas #ffffff, muted text #676b73, text #111111; 20px radius; padding 8px 20px; type 12px
- **content card (variant 2)**: colors: surface #ecedee, canvas #ffffff, muted text #676b73; 10px radius; type 12px; translucent backdrop with blur (solid fallback)
- **pill badge**: colors: accent #000aff, canvas #ffffff; 30px radius; padding 4px 8px
- **pill badge (variant 2)**: colors: divider (decorative) #a1a4aa, canvas #ffffff; 30px radius; padding 4px 8px
- **secondary button**: fill canvas #ffffff; label text #111111; 10px radius; padding 12px 24px; 1px border
- **feature card**: colors: text #111111, muted text #676b73, canvas #ffffff; type 12px
- **top navigation bar (variant 2)**: colors: surface #ecedee, muted text #676b73; 10px radius; 1px border
- **logo row**: colors: canvas #ffffff, surface #ecedee; 6px radius; 1px border
- opacity and color transitions only, 150ms ease-out
- every interactive element shows a 2px #000aff focus ring with 2px offset
- primary action darkens or lightens by one step on hover and keeps its label color
- 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[]}, Metric{value, label}, 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 #000aff 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 #111111 on #ffffff = 18.88:1; body text on surface #111111 on #ecedee = 16.11:1; muted text on canvas #676b73 on #ffffff = 5.35:1; muted text on surface #676b73 on #ecedee = 4.56:1; primary action label on fill #ffffff on #000aff = 8.44:1; link text on canvas #000aff on #ffffff = 8.44:1; focus ring on canvas #000aff on #ffffff = 8.44:1; focus ring on surface #000aff on #ecedee = 7.2:1; input border on canvas #84878f on #ffffff = 3.59:1; accent icons and active marks on canvas #000aff on #ffffff = 8.44:1; text on inverse band #ffffff on #3b3b3b = 11.2: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 (#000aff fill, #ffffff label) and use it once per view; secondary actions stay outlined or text-only.
- Use the blue accent for small marks only (links, active states, icons), at most two or three times per screen.
- Keep the 10px control radius consistent across buttons, inputs and chips.
- Limit headline sizes to the type scale; the 128px 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