Skip to main content
vibld

Style gallery

Sandpoint

Warm minimal online store site on white with a sparing vermilion accent

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

A light, restrained, on warm neutrals visual system for a consumer brand store. Its look rests on heavy 700-weight display type up to 56px, tight display tracking (-0.050em) and a sparing vermilion accent on a white canvas. Use it as a complete starting point: tokens, type scale, component specs, page rhythm and guardrails are all included.

Build in this styleRead the build prompt

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

What makes it

  • heavy 700-weight display type up to 56px
  • tight display tracking (-0.050em)
  • short uppercase labels with open tracking
  • small 7px corners on controls
  • large 18px card corners
  • no shadows; depth comes from surface tone steps
  • one vermilion accent used sparingly

Colors

Warm, quiet, trustworthy. The white canvas and tight display tracking (-0.050em) carry most of the character.

  • canvas#fffffb
  • surface / primary action label#ffffff
  • text / primary action fill#000000
  • muted text#707070
  • divider (decorative) / input border#303030
  • accent / focus ring#ff611f
  • link text#d63f00

Every checked pair, measured again

SampleWhereRatioNeeds
Aabody text on canvas20.95:14.5:1
Aabody text on surface21.00:14.5:1
Aamuted text on canvas4.94:14.5:1
Aamuted text on surface4.95:14.5:1
Aaprimary action label on fill21.00:14.5:1
Aalink text on canvas4.58:14.5:1
focus ring on canvas3.00:13:1
focus ring on surface3.01:13:1
input border on canvas13.17:13:1
accent icons and active marks on canvas3.00:13:1

Typefaces

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

Type scale

56px Inter 700

53px Inter 700

30px Inter 400

24px Inter 400

18px Inter 400

16px Inter 400

12px Inter 400

Corners and shadows

  • cards: 18px
  • links: 7px
  • inputs: 7px
  • buttons: 7px
  • small-interactive: 14px

No shadows: depth comes from surfaces and lines.

Spacing and imagery

comfortable density on a 4px base unit; container 1440px; section gap 100px; card padding 20px-24px; element gap 4px-8px; radii cards 18px, links 7px, inputs 7px, buttons 7px, small-interactive 14px; no shadows

Photography, data graphics. Use placeholder or generated imagery only; partner marks are neutral placeholders in the muted text color. 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. left-aligned hero: oversized headline, short lede and a primary plus secondary action
  3. large framed product view on a tinted surface
  4. tabbed showcase that swaps a panel per tab
  5. metrics band with three or four large figures and captions
  6. product grid: image, name, price and quick-add, 4 columns desktop / 2 mobile
  7. article or story cards with image, kicker, title and date
  8. footer with grouped link columns, legal line and social icons
  9. content sits in a 1440px centered container with 24px side padding (16px on mobile)
  10. sections are separated by 100px of vertical space on desktop, roughly half that on mobile

Patterns

  • hero
  • large framed product view on a tinted surface
  • tabbed showcase that swaps a panel per tab
  • metrics band with three or four large figures and captions
  • product grid
  • article or story cards with image, kicker, title and date

Components

  • tabs: colors: accent #ff611f, surface #ffffff; sticky
  • top navigation bar: colors: surface #ffffff, text #000000; type 14px/500; soft shadow; uppercase with at least 0.05em tracking
  • hero block: follows the shared tokens
  • pill badge: colors: surface #ffffff, canvas #fffffb; no shadow
  • primary button: fill #000000, label #ffffff; 7px radius; type 14px/500; uppercase with at least 0.05em tracking
  • secondary button: transparent fill; 7px radius
  • secondary button (variant 2): fill surface #ffffff
  • pill badge (variant 2): colors: surface #ffffff, text #000000; 14px radius; soft shadow
  • top navigation bar (variant 2): colors: text #000000; type 13px/900

Interactions and states

  • opacity and color transitions only, 150ms ease-out
  • every interactive element shows a 2px #ff611f focus ring with 2px offset
  • primary action darkens or lightens by one step on hover and keeps its label color
  • tabs switch panels without a page load; arrow keys move between tabs
  • 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
  • selected and unselected tab states, with the panel labeled by its tab
  • 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 (#000000 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 7px control radius consistently; do not mix in pill shapes.
  • Limit headline sizes to the type scale; the 56px display size appears once per page, in the hero.
  • Separate layers with surface tone and hairlines, not shadows.
  • 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 #ff611f 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.
  • Tabs follow the ARIA tabs pattern with roving tabindex.
  • 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 "Sandpoint" style: restrained, on warm neutrals, with heavy 700-weight display type up to 56px, tight display tracking (-0.050em), 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:
- top navigation: wordmark left, 4-6 text links, primary action right; collapses to a menu sheet under 768px
- left-aligned hero: oversized headline, short lede and a primary plus secondary action
- large framed product view on a tinted surface
- tabbed showcase that swaps a panel per tab
- metrics band with three or four large figures and captions
- product grid: image, name, price and quick-add, 4 columns desktop / 2 mobile
- article or story cards with image, kicker, title and date
- 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 100px 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: #fffffb;
  --color-surface: #ffffff;
  --color-text: #000000;
  --color-muted-text: #707070;
  --color-divider: #303030;
  --color-accent: #ff611f;
  --color-link-text: #d63f00;
  --text-12: 12px;
  --text-16: 16px;
  --text-18: 18px;
  --text-24: 24px;
  --text-30: 30px;
  --text-53: 53px;
  --text-56: 56px;
  --radius-cards: 18px;
  --radius-links: 7px;
  --radius-inputs: 7px;
  --radius-buttons: 7px;
  --radius-small-interactive: 14px;
  --space-unit: 4px;
  --container: 1440px;
}
```
Display Inter, body Inter (Google Fonts, self-hosted, font-display: swap).
Type scale (size/weight/line-height tracking): 12px/400/1.6, 16px/400/1.5, 18px/400/1.5, 24px/400/1.14, 30px/400/1.0 -0.040em, 53px/700/1.0 -0.050em, 56px/700/1.0 -0.050em.
Spacing: comfortable density on a 4px base unit; container 1440px; section gap 100px; card padding 20px-24px; element gap 4px-8px; radii cards 18px, links 7px, inputs 7px, buttons 7px, small-interactive 14px; no shadows.
Signature moves: heavy 700-weight display type up to 56px; tight display tracking (-0.050em); short uppercase labels with open tracking; small 7px corners on controls; large 18px card corners; no shadows; depth comes from surface tone steps; one vermilion accent used sparingly.

### Components & interactions
- **tabs**: colors: accent #ff611f, surface #ffffff; sticky
- **top navigation bar**: colors: surface #ffffff, text #000000; type 14px/500; soft shadow; uppercase with at least 0.05em tracking
- **hero block**: follows the shared tokens
- **pill badge**: colors: surface #ffffff, canvas #fffffb; no shadow
- **primary button**: fill #000000, label #ffffff; 7px radius; type 14px/500; uppercase with at least 0.05em tracking
- **secondary button**: transparent fill; 7px radius
- **secondary button (variant 2)**: fill surface #ffffff
- **pill badge (variant 2)**: colors: surface #ffffff, text #000000; 14px radius; soft shadow
- **top navigation bar (variant 2)**: colors: text #000000; type 13px/900
- opacity and color transitions only, 150ms ease-out
- every interactive element shows a 2px #ff611f focus ring with 2px offset
- primary action darkens or lightens by one step on hover and keeps its label color
- tabs switch panels without a page load; arrow keys move between tabs
- 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: Post{slug, title, kicker, excerpt, coverUrl, publishedAt}, Product{slug, name, price, imageUrl, alt, inStock, swatches[]}, Metric{value, label}, 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
- selected and unselected tab states, with the panel labeled by its tab
- 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 #ff611f 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.
- Tabs follow the ARIA tabs pattern with roving tabindex.
- 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 #000000 on #fffffb = 20.95:1; body text on surface #000000 on #ffffff = 21.0:1; muted text on canvas #707070 on #fffffb = 4.94:1; muted text on surface #707070 on #ffffff = 4.95:1; primary action label on fill #ffffff on #000000 = 21.0:1; link text on canvas #d63f00 on #fffffb = 4.58:1; focus ring on canvas #ff611f on #fffffb = 3.0:1; focus ring on surface #ff611f on #ffffff = 3.01:1; input border on canvas #303030 on #fffffb = 13.17:1; accent icons and active marks on canvas #ff611f on #fffffb = 3.0: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 (#000000 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 7px control radius consistently; do not mix in pill shapes.
- Limit headline sizes to the type scale; the 56px display size appears once per page, in the hero.
- Separate layers with surface tone and hairlines, not shadows.
- 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