Cressbarrow

A dark and atmospheric visual system for a creative studio. Its look rests on light 300-weight display type up to 116px, serif headlines over a sans-serif body and a monochrome palette on a near-black 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 Cressbarrow.

What makes it

• light 300-weight display type up to 116px
• serif headlines over a sans-serif body
• pill-shaped buttons
• no shadows; depth comes from surface tone steps
• very generous vertical spacing between sections

Colors

Dramatic, immersive, premium. A near-black ground, light 300-weight display type up to 116px and a monochrome palette set the tone.

• canvas#000000
• surface#1d1d1d
• text / primary action fill / focus ring#ffffff
• muted text#a1a1aa
• divider (decorative) / input border#d6d5d0
• primary action label#111111

Every checked pair, measured again

Typefaces

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

• Source Serif 4Headings
• InterBody

Type scale

Corners and shadows

• tags: 9999px
• cards: 8px
• buttons: 9999px

No shadows: depth comes from surfaces and lines.

Spacing and imagery

comfortable density on a 8px base unit; container 1440px; section gap 128px-144px; card padding 24px; element gap 24px-32px; radii tags 9999px, cards 8px, buttons 9999px; 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. alternating two-column text-and-visual blocks
4. article or story cards with image, kicker, title and date
5. large framed product view on a tinted surface
6. feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
7. tabbed showcase that swaps a panel per tab
8. metrics band with three or four large figures and captions
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 128px-144px of vertical space on desktop, roughly half that on mobile

Patterns

• hero
• alternating two-column text-and-visual blocks
• article or story cards with image, kicker, title and date
• large framed product view on a tinted surface
• 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
• metrics band with three or four large figures and captions

Components

• primary button: fill #ffffff, label #111111; 9999px radius
• top navigation bar: colors: canvas #000000, text #ffffff; soft shadow; underlined
• hero block: colors: canvas #000000, text #ffffff
• product frame: colors: surface #1d1d1d, text #ffffff; uppercase with at least 0.05em tracking
• pill badge: colors: text #ffffff, canvas #000000; pill radius; no shadow
• secondary button: fill text #ffffff; label canvas #000000; pill radius; padding 12px 24px; no shadow
• text input: colors: surface #1d1d1d, divider (decorative) #d6d5d0, text #ffffff; underlined

Interactions and states

• sections fade and rise 12px into view (200ms, staggered 60ms)
• every interactive element shows a 2px #ffffff 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

Guardrails

Experience

• Keep one primary action style (#ffffff fill, #111111 label) and use it once per view; secondary actions stay outlined or text-only.
• Buttons and chips are pills; cards keep their own radius so the two read differently.
• Limit headline sizes to the type scale; the 116px 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 #ffffff 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.
• Light display weights are used only at 24px and above; body copy stays at 400 or heavier.
• 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.

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 dark-theme marketing site for a fictional creative studio in the "Cressbarrow" style: dark and atmospheric, with light 300-weight display type up to 116px, serif headlines over a sans-serif body, pill-shaped buttons. Use invented copy and placeholder imagery throughout.

### Stack
Astro, TypeScript, Tailwind CSS, React islands with Radix primitives (tabs, accordion, dialog), Lucide icons, Motion, 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
- alternating two-column text-and-visual blocks
- article or story cards with image, kicker, title and date
- large framed product view on a tinted surface
- 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
- metrics band with three or four large figures and captions
- 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 128px-144px 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: #000000;
  --color-surface: #1d1d1d;
  --color-text: #ffffff;
  --color-muted-text: #a1a1aa;
  --color-divider: #d6d5d0;
  --color-primary-action-label: #111111;
  --text-16: 16px;
  --text-22: 22px;
  --text-72: 72px;
  --text-82: 82px;
  --text-116: 116px;
  --radius-tags: 9999px;
  --radius-cards: 8px;
  --radius-buttons: 9999px;
  --space-unit: 8px;
  --container: 1440px;
}
```
Display Source Serif 4, body Inter (Google Fonts, self-hosted, font-display: swap).
Type scale (size/weight/line-height tracking): 16px/400/1.5, 22px/400/1.3, 72px/300/1.1 -0.009em, 82px/300/1.05 -0.009em, 116px/300/1.05 -0.018em.
Spacing: comfortable density on a 8px base unit; container 1440px; section gap 128px-144px; card padding 24px; element gap 24px-32px; radii tags 9999px, cards 8px, buttons 9999px; no shadows.
Signature moves: light 300-weight display type up to 116px; serif headlines over a sans-serif body; pill-shaped buttons; no shadows; depth comes from surface tone steps; very generous vertical spacing between sections.

### Components & interactions
- **primary button**: fill #ffffff, label #111111; 9999px radius
- **top navigation bar**: colors: canvas #000000, text #ffffff; soft shadow; underlined
- **hero block**: colors: canvas #000000, text #ffffff
- **product frame**: colors: surface #1d1d1d, text #ffffff; uppercase with at least 0.05em tracking
- **pill badge**: colors: text #ffffff, canvas #000000; pill radius; no shadow
- **secondary button**: fill text #ffffff; label canvas #000000; pill radius; padding 12px 24px; no shadow
- **text input**: colors: surface #1d1d1d, divider (decorative) #d6d5d0, text #ffffff; underlined
- sections fade and rise 12px into view (200ms, staggered 60ms)
- every interactive element shows a 2px #ffffff 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}, 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

### Accessibility
- Text, links, focus rings and input borders use only the verified pairs listed in contrast checks.
- Focus ring: 2px solid #ffffff 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.
- Light display weights are used only at 24px and above; body copy stays at 400 or heavier.
- 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 #ffffff on #000000 = 21.0:1; body text on surface #ffffff on #1d1d1d = 16.86:1; muted text on canvas #a1a1aa on #000000 = 8.19:1; muted text on surface #a1a1aa on #1d1d1d = 6.58:1; primary action label on fill #111111 on #ffffff = 18.88:1; focus ring on canvas #ffffff on #000000 = 21.0:1; focus ring on surface #ffffff on #1d1d1d = 16.86:1; input border on canvas #d6d5d0 on #000000 = 14.29: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 (#ffffff fill, #111111 label) and use it once per view; secondary actions stay outlined or text-only.
- Buttons and chips are pills; cards keep their own radius so the two read differently.
- Limit headline sizes to the type scale; the 116px 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