Skip to main content
vibld

Style gallery

Briardun

Monochrome minimal B2B software site on off-white with a sparing vermilion accent

Light · Monochrome minimal · SaaS · static site

A light style preset for a software product, near-monochrome and restrained in character. Its look rests on heavy 700-weight display type up to 128px, tight display tracking (-0.030em) and a sparing vermilion accent on an off-white canvas. Every value needed to rebuild the look is recorded, from color roles and type steps to spacing, radii and component specs.

Build in this styleRead the build prompt

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

What makes it

  • heavy 700-weight display type up to 128px
  • tight display tracking (-0.030em)
  • sans-serif headlines over a serif body
  • monospace used for labels, metadata or code
  • small 8px corners on controls
  • large 24px card corners
  • one subtle shadow for raised elements
  • one vermilion accent used sparingly

Colors

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

  • canvas / text on band#f9f9f9
  • surface / primary action label#ffffff
  • text#202020
  • muted text#646464
  • divider (decorative), never behind text#e1e4e8
  • input border#8692a2
  • accent / focus ring#fa4616
  • primary action fill#e03305
  • link text#d83105
  • inverse band#0a0a0a
  • supporting accent (decorative), never behind text#b62600

Every checked pair, measured again

SampleWhereRatioNeeds
Aabody text on canvas15.48:14.5:1
Aabody text on surface16.29:14.5:1
Aamuted text on canvas5.62:14.5:1
Aamuted text on surface5.92:14.5:1
Aaprimary action label on fill4.52:14.5:1
Aalink text on canvas4.57:14.5:1
focus ring on canvas3.35:13:1
focus ring on surface3.53:13:1
input border on canvas3.00:13:1
accent icons and active marks on canvas3.35:13:1
Aatext on inverse band18.80:14.5:1

Typefaces

monospace accents in Roboto Mono; 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
  • Source Serif 4Body
  • Roboto MonoFigures and code

Type scale

128px Inter 700

56px Inter 700

20px Source Serif 4 400

16px Source Serif 4 400

12px Source Serif 4 400

Corners and shadows

  • cards: 24px
  • buttons: 8px
  • small-elements: 4px
  • large-containers: 16px
  • shadow-1: rgb(182, 38, 0) 0px 3px 0px 0px

Spacing and imagery

comfortable density on a 8px base unit; container 1200px; section gap 64px-80px; card padding 24px; element gap 24px; radii cards 24px, buttons 8px, small-elements 4px, large-containers 16px; 1 shadow level

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. top navigation: wordmark left, 4-6 text links, primary action right; collapses to a menu sheet under 768px
  2. centered hero: headline, one-line lede and a primary plus secondary action, visual below
  3. horizontal card rail with previous/next buttons and snap scrolling
  4. tabbed showcase that swaps a panel per tab
  5. alternating two-column text-and-visual blocks
  6. large framed product view on a tinted surface
  7. row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
  8. footer with grouped link columns, legal line and social icons
  9. content sits in a 1200px centered container with 24px side padding (16px on mobile)
  10. sections are separated by 64px-80px of vertical space on desktop, roughly half that on mobile

Patterns

  • hero
  • horizontal card rail with previous/next buttons and snap scrolling
  • tabbed showcase that swaps a panel per tab
  • alternating two-column text-and-visual blocks
  • large framed product view on a tinted surface
  • row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)

Components

  • primary button: fill #e03305, label #ffffff; 8px radius; padding 12px 24px; type 16px; soft shadow
  • primary button (variant 2): fill #e03305, label #ffffff; 8px radius; padding 12px 24px; 1px border; type 16px; no shadow
  • top navigation bar: colors: surface #ffffff, muted text #646464; type 14px/500; no shadow
  • hero block: colors: text #202020
  • content card: colors: surface #ffffff, canvas #f9f9f9; 24px radius; soft shadow
  • pill badge: colors: surface #ffffff, text #202020, muted text #646464; 8px radius; type 14px/600; soft shadow
  • content card (variant 2): colors: inverse band #0a0a0a
  • footer: colors: surface #ffffff, muted text #646464; type 13px/400
  • pill badge (variant 2): colors: text #202020; type 14px/500
  • hero block (variant 2): colors: canvas #f9f9f9

Interactions and states

  • opacity and color transitions only, 150ms ease-out
  • every interactive element shows a 2px #fa4616 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

Guardrails

Experience

  • Keep one primary action style (#e03305 fill, #ffffff label) and use it once per view; secondary actions stay outlined or text-only.
  • Use the vermilion accent for small marks only (links, active states, icons), at most two or three times per screen.
  • Use the 8px control radius consistently; do not mix in pill shapes.
  • Limit headline sizes to the type scale; the 128px display size appears once per page, in the hero.
  • 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 #fa4616 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.
  • 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.

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 software product in the "Briardun" style: near-monochrome and restrained, with heavy 700-weight display type up to 128px, tight display tracking (-0.030em), sans-serif headlines over a serif body. Use invented copy and placeholder imagery throughout.

### Stack
Astro, TypeScript, Tailwind CSS, React islands with Radix primitives (tabs, accordion, dialog), Lucide icons, 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:
- 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
- horizontal card rail with previous/next buttons and snap scrolling
- tabbed showcase that swaps a panel per tab
- alternating two-column text-and-visual blocks
- large framed product view on a tinted surface
- row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
- footer with grouped link columns, legal line and social icons
- content sits in a 1200px centered container with 24px side padding (16px on mobile)
- sections are separated by 64px-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: #f9f9f9;
  --color-surface: #ffffff;
  --color-text: #202020;
  --color-muted-text: #646464;
  --color-divider: #e1e4e8;
  --color-input-border: #8692a2;
  --color-accent: #fa4616;
  --color-primary-action-fill: #e03305;
  --color-link-text: #d83105;
  --color-inverse-band: #0a0a0a;
  --color-supporting-accent: #b62600;
  --text-12: 12px;
  --text-16: 16px;
  --text-20: 20px;
  --text-56: 56px;
  --text-128: 128px;
  --radius-cards: 24px;
  --radius-buttons: 8px;
  --radius-small-elements: 4px;
  --radius-large-containers: 16px;
  --space-unit: 8px;
  --container: 1200px;
  --shadow-1: rgb(182, 38, 0) 0px 3px 0px 0px;
}
```
Display Inter, body Source Serif 4, mono Roboto Mono (Google Fonts, self-hosted, font-display: swap).
Type scale (size/weight/line-height tracking): 12px/400/1.5, 16px/400/1.5, 20px/400/1.4 -0.016em, 56px/700/1.0 -0.030em, 128px/700/1.0 -0.030em.
Spacing: comfortable density on a 8px base unit; container 1200px; section gap 64px-80px; card padding 24px; element gap 24px; radii cards 24px, buttons 8px, small-elements 4px, large-containers 16px; 1 shadow level.
Signature moves: heavy 700-weight display type up to 128px; tight display tracking (-0.030em); sans-serif headlines over a serif body; monospace used for labels, metadata or code; small 8px corners on controls; large 24px card corners; one subtle shadow for raised elements; one vermilion accent used sparingly.

### Components & interactions
- **primary button**: fill #e03305, label #ffffff; 8px radius; padding 12px 24px; type 16px; soft shadow
- **primary button (variant 2)**: fill #e03305, label #ffffff; 8px radius; padding 12px 24px; 1px border; type 16px; no shadow
- **top navigation bar**: colors: surface #ffffff, muted text #646464; type 14px/500; no shadow
- **hero block**: colors: text #202020
- **content card**: colors: surface #ffffff, canvas #f9f9f9; 24px radius; soft shadow
- **pill badge**: colors: surface #ffffff, text #202020, muted text #646464; 8px radius; type 14px/600; soft shadow
- **content card (variant 2)**: colors: inverse band #0a0a0a
- **footer**: colors: surface #ffffff, muted text #646464; type 13px/400
- **pill badge (variant 2)**: colors: text #202020; type 14px/500
- **hero block (variant 2)**: colors: canvas #f9f9f9
- opacity and color transitions only, 150ms ease-out
- every interactive element shows a 2px #fa4616 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}, 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

### Accessibility
- Text, links, focus rings and input borders use only the verified pairs listed in contrast checks.
- Focus ring: 2px solid #fa4616 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.
- 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 #202020 on #f9f9f9 = 15.48:1; body text on surface #202020 on #ffffff = 16.29:1; muted text on canvas #646464 on #f9f9f9 = 5.62:1; muted text on surface #646464 on #ffffff = 5.92:1; primary action label on fill #ffffff on #e03305 = 4.52:1; link text on canvas #d83105 on #f9f9f9 = 4.57:1; focus ring on canvas #fa4616 on #f9f9f9 = 3.35:1; focus ring on surface #fa4616 on #ffffff = 3.53:1; input border on canvas #8692a2 on #f9f9f9 = 3.0:1; accent icons and active marks on canvas #fa4616 on #f9f9f9 = 3.35:1; text on inverse band #f9f9f9 on #0a0a0a = 18.8: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.

### 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 (#e03305 fill, #ffffff label) and use it once per view; secondary actions stay outlined or text-only.
- Use the vermilion accent for small marks only (links, active states, icons), at most two or three times per screen.
- Use the 8px control radius consistently; do not mix in pill shapes.
- Limit headline sizes to the type scale; the 128px display size appears once per page, in the hero.
- 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