Skip to main content
vibld

Style gallery

Sloehall

Bold graphic online store site on off-white with a red lead color

Light · Bold graphic · E-commerce · front-end app (local state)

A light style preset for a consumer brand store, loud, poster-like in character. Its look rests on heavy 700-weight display type up to 30px, short uppercase labels with open tracking and a red lead color on an off-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 Sloehall.

What makes it

  • heavy 700-weight display type up to 30px
  • short uppercase labels with open tracking
  • square corners on controls (0-2px)
  • no shadows; depth comes from surface tone steps
  • several saturated colors used as section and card fills
  • compact, information-dense spacing

Colors

Confident, graphic, high-impact. An off-white ground, heavy 700-weight display type up to 30px and a red lead color set the tone.

  • canvas#f6f6f6
  • surface#ffffff
  • text#0a0a0a
  • muted text#52525b
  • divider (decorative), never behind text#e6e6e6
  • input border#8e8e8e
  • accent / primary action fill / focus ring#ff0000
  • primary action label#111111
  • link text#e30000

Every checked pair, measured again

SampleWhereRatioNeeds
Aabody text on canvas18.32:14.5:1
Aabody text on surface19.80:14.5:1
Aamuted text on canvas7.15:14.5:1
Aamuted text on surface7.73:14.5:1
Aaprimary action label on fill4.72:14.5:1
Aalink text on canvas4.55:14.5:1
focus ring on canvas3.70:13:1
focus ring on surface4.00:13:1
input border on canvas3.03:13:1
accent icons and active marks on canvas3.70: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

30px Inter 400

16px Inter 400

Corners and shadows

  • nav: 0px
  • cards: 0px
  • buttons: 0px

No shadows: depth comes from surfaces and lines.

Spacing and imagery

compact density on a 4px base unit; container 1440px; section gap 100px; card padding 10px; element gap 8px-10px; radii nav 0px, cards 0px, buttons 0px; 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. 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. feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
  4. alternating two-column text-and-visual blocks
  5. large framed product view on a tinted surface
  6. metrics band with three or four large figures and captions
  7. product grid: image, name, price and quick-add, 4 columns desktop / 2 mobile
  8. article or story cards with image, kicker, title and date
  9. footer with grouped link columns, legal line and social icons
  10. content sits in a 1440px centered container with 24px side padding (16px on mobile)
  11. sections are separated by 100px of vertical space on desktop, roughly half that on mobile

Patterns

  • hero
  • feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
  • alternating two-column text-and-visual blocks
  • large framed product view on a tinted surface
  • metrics band with three or four large figures and captions
  • product grid
  • article or story cards with image, kicker, title and date

Components

  • primary button: fill #ff0000, label #111111; 0px radius
  • secondary button: transparent fill; label text #0a0a0a; 0px radius; uppercase with at least 0.05em tracking
  • secondary button (variant 2): transparent fill; 0px radius; 0.5px border; uppercase with at least 0.05em tracking
  • hero block: colors: text #0a0a0a; type 30px; uppercase with at least 0.05em tracking; underlined
  • pill badge: colors: text #0a0a0a; uppercase with at least 0.05em tracking
  • announcement strip: colors: text #0a0a0a, input border #8e8e8e, canvas #f6f6f6; uppercase with at least 0.05em tracking
  • content card: colors: accent #ff0000
  • content card (variant 2): colors: canvas #f6f6f6, surface #ffffff; no shadow
  • text link: colors: text #0a0a0a; uppercase with at least 0.05em tracking

Interactions and states

  • hard-cut hover states: fills invert instantly, no easing on color
  • every interactive element shows a 2px #ff0000 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 (#ff0000 fill, #111111 label) and use it once per view; secondary actions stay outlined or text-only.
  • Give each saturated color a job (section, category or state) and keep text on neutral surfaces.
  • Keep corners square on every control; do not mix in rounded or pill shapes.
  • Limit headline sizes to the type scale; the 30px 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 #ff0000 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.

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 "Sloehall" style: loud, poster-like, with heavy 700-weight display type up to 30px, short uppercase labels with open tracking, square corners on controls (0-2px). 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
- centered hero: headline, one-line lede and a primary plus secondary action, visual below
- feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
- alternating two-column text-and-visual blocks
- large framed product view on a tinted surface
- 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: #f6f6f6;
  --color-surface: #ffffff;
  --color-text: #0a0a0a;
  --color-muted-text: #52525b;
  --color-divider: #e6e6e6;
  --color-input-border: #8e8e8e;
  --color-accent: #ff0000;
  --color-primary-action-label: #111111;
  --color-link-text: #e30000;
  --text-16: 16px;
  --text-30: 30px;
  --radius-nav: 0px;
  --radius-cards: 0px;
  --radius-buttons: 0px;
  --space-unit: 4px;
  --container: 1440px;
}
```
Display Inter, body Inter (Google Fonts, self-hosted, font-display: swap).
Type scale (size/weight/line-height tracking): 16px/400/1.5, 30px/400/1.0 0.040em.
Spacing: compact density on a 4px base unit; container 1440px; section gap 100px; card padding 10px; element gap 8px-10px; radii nav 0px, cards 0px, buttons 0px; no shadows.
Signature moves: heavy 700-weight display type up to 30px; short uppercase labels with open tracking; square corners on controls (0-2px); no shadows; depth comes from surface tone steps; several saturated colors used as section and card fills; compact, information-dense spacing.

### Components & interactions
- **primary button**: fill #ff0000, label #111111; 0px radius
- **secondary button**: transparent fill; label text #0a0a0a; 0px radius; uppercase with at least 0.05em tracking
- **secondary button (variant 2)**: transparent fill; 0px radius; 0.5px border; uppercase with at least 0.05em tracking
- **hero block**: colors: text #0a0a0a; type 30px; uppercase with at least 0.05em tracking; underlined
- **pill badge**: colors: text #0a0a0a; uppercase with at least 0.05em tracking
- **announcement strip**: colors: text #0a0a0a, input border #8e8e8e, canvas #f6f6f6; uppercase with at least 0.05em tracking
- **content card**: colors: accent #ff0000
- **content card (variant 2)**: colors: canvas #f6f6f6, surface #ffffff; no shadow
- **text link**: colors: text #0a0a0a; uppercase with at least 0.05em tracking
- hard-cut hover states: fills invert instantly, no easing on color
- every interactive element shows a 2px #ff0000 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}, 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 #ff0000 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.
Verified contrast: body text on canvas #0a0a0a on #f6f6f6 = 18.32:1; body text on surface #0a0a0a on #ffffff = 19.8:1; muted text on canvas #52525b on #f6f6f6 = 7.15:1; muted text on surface #52525b on #ffffff = 7.73:1; primary action label on fill #111111 on #ff0000 = 4.72:1; link text on canvas #e30000 on #f6f6f6 = 4.55:1; focus ring on canvas #ff0000 on #f6f6f6 = 3.7:1; focus ring on surface #ff0000 on #ffffff = 4.0:1; input border on canvas #8e8e8e on #f6f6f6 = 3.03:1; accent icons and active marks on canvas #ff0000 on #f6f6f6 = 3.7: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 (#ff0000 fill, #111111 label) and use it once per view; secondary actions stay outlined or text-only.
- Give each saturated color a job (section, category or state) and keep text on neutral surfaces.
- Keep corners square on every control; do not mix in rounded or pill shapes.
- Limit headline sizes to the type scale; the 30px 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