Style gallery
Cairnmill
Dark cinematic design tool site on near-black with a sparing yellow accent
Dark · Dark cinematic · Design tools · static site
A dark and atmospheric dark-theme style for a creative software product website. Its look rests on 500-weight display type up to 96px, sans-serif headlines over a serif body and a sparing yellow accent 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 Cairnmill.
What makes it
- 500-weight display type up to 96px
- sans-serif headlines over a serif body
- pill-shaped buttons
- large 28px card corners
- no shadows; depth comes from surface tone steps
- one yellow accent used sparingly
- compact, information-dense spacing
Colors
Dramatic, immersive, premium. The near-black canvas and sans-serif headlines over a serif body carry most of the character.
- canvas / primary action label
#000000 - surface
#18181b - text
#ffffff - muted text
#a8afb7 - divider (decorative), never behind text
#343538 - input border
#63656a - accent / primary action fill / link text / focus ring
#fde533
Every checked pair, measured again
| Sample | Where | Ratio | Needs |
|---|---|---|---|
| Aa | body text on canvas | 21.00:1 | 4.5:1 |
| Aa | body text on surface | 17.72:1 | 4.5:1 |
| Aa | muted text on canvas | 9.48:1 | 4.5:1 |
| Aa | muted text on surface | 8.00:1 | 4.5:1 |
| Aa | primary action label on fill | 16.43:1 | 4.5:1 |
| Aa | link text on canvas | 16.43:1 | 4.5:1 |
| focus ring on canvas | 16.43:1 | 3:1 | |
| focus ring on surface | 13.86:1 | 3:1 | |
| input border on canvas | 3.60:1 | 3:1 | |
| accent icons and active marks on canvas | 16.43:1 | 3:1 |
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
- InterHeadings
- Source Serif 4Body
Type scale
96px Inter 500
65px Inter 500
28px Inter 400
24px Source Serif 4 400
19px Source Serif 4 400
16px Source Serif 4 400
14px Source Serif 4 400
12px Source Serif 4 400
Corners and shadows
- cards:
28px - large:
40px - tiles:
20px - badges:
9999px - subtle:
4px - buttons:
9999px
No shadows: depth comes from surfaces and lines.
Spacing and imagery
compact density on a 4px base unit; container 1200px; section gap 64px; card padding 32px; element gap 8px; radii cards 28px, large 40px, tiles 20px, badges 9999px, subtle 4px, 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
- 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
- large framed product view on a tinted surface
- row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
- feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
- pricing tiers with one highlighted plan and a monthly/yearly toggle
- 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 of vertical space on desktop, roughly half that on mobile
Patterns
- hero
- 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)
- feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
- pricing tiers with one highlighted plan and a monthly/yearly toggle
Components
- primary button: fill #fde533, label #000000; pill radius; padding 10px 16px; type 14px
- secondary button: fill divider (decorative) #343538; label divider (decorative) #343538; pill radius; padding 10px 16px; type 14px
- secondary button (variant 2): transparent fill; label divider (decorative) #343538; pill radius; padding 4px 12px; 1px border; type 12px
- pill badge: colors: accent #fde533, canvas #000000; pill radius; padding 4px 8px; type 12px
- content card: colors: surface #18181b, divider (decorative) #343538, text #ffffff; 20px radius; padding 32px; 1px border
- product frame: colors: surface #18181b, divider (decorative) #343538; 20px radius
- product frame (variant 2): colors: surface #18181b
- top navigation bar: colors: canvas #000000, text #ffffff
- hero block: colors: text #ffffff
- diagram: colors: muted text #a8afb7; type 16px/400
- content card (variant 2): colors: surface #18181b, divider (decorative) #343538, text #ffffff; 28px radius; padding 32px; 1px border
- feature card: colors: text #ffffff
Interactions and states
- sections fade and rise 12px into view (200ms, staggered 60ms)
- every interactive element shows a 2px #fde533 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 (#fde533 fill, #000000 label) and use it once per view; secondary actions stay outlined or text-only.
- Use the yellow accent for small marks only (links, active states, icons), at most two or three times per screen.
- Buttons and chips are pills; cards keep their own radius so the two read differently.
- Limit headline sizes to the type scale; the 96px 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 #fde533 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.
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 dark-theme marketing site for a fictional creative software product in the "Cairnmill" style: dark and atmospheric, with 500-weight display type up to 96px, sans-serif headlines over a 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
- large framed product view on a tinted surface
- row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
- feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
- pricing tiers with one highlighted plan and a monthly/yearly toggle
- 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 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: #18181b;
--color-text: #ffffff;
--color-muted-text: #a8afb7;
--color-divider: #343538;
--color-input-border: #63656a;
--color-accent: #fde533;
--text-12: 12px;
--text-14: 14px;
--text-16: 16px;
--text-19: 19px;
--text-24: 24px;
--text-28: 28px;
--text-65: 65px;
--text-96: 96px;
--radius-cards: 28px;
--radius-large: 40px;
--radius-tiles: 20px;
--radius-badges: 9999px;
--radius-subtle: 4px;
--radius-buttons: 9999px;
--space-unit: 4px;
--container: 1200px;
}
```
Display Inter, body Source Serif 4 (Google Fonts, self-hosted, font-display: swap).
Type scale (size/weight/line-height tracking): 12px/400/1.5, 14px/400/1.75, 16px/400/1.75, 19px/400/1.5, 24px/400/1.2, 28px/400/1.0, 65px/500/1.0, 96px/500/0.9.
Spacing: compact density on a 4px base unit; container 1200px; section gap 64px; card padding 32px; element gap 8px; radii cards 28px, large 40px, tiles 20px, badges 9999px, subtle 4px, buttons 9999px; no shadows.
Signature moves: 500-weight display type up to 96px; sans-serif headlines over a serif body; pill-shaped buttons; large 28px card corners; no shadows; depth comes from surface tone steps; one yellow accent used sparingly; compact, information-dense spacing.
### Components & interactions
- **primary button**: fill #fde533, label #000000; pill radius; padding 10px 16px; type 14px
- **secondary button**: fill divider (decorative) #343538; label divider (decorative) #343538; pill radius; padding 10px 16px; type 14px
- **secondary button (variant 2)**: transparent fill; label divider (decorative) #343538; pill radius; padding 4px 12px; 1px border; type 12px
- **pill badge**: colors: accent #fde533, canvas #000000; pill radius; padding 4px 8px; type 12px
- **content card**: colors: surface #18181b, divider (decorative) #343538, text #ffffff; 20px radius; padding 32px; 1px border
- **product frame**: colors: surface #18181b, divider (decorative) #343538; 20px radius
- **product frame (variant 2)**: colors: surface #18181b
- **top navigation bar**: colors: canvas #000000, text #ffffff
- **hero block**: colors: text #ffffff
- **diagram**: colors: muted text #a8afb7; type 16px/400
- **content card (variant 2)**: colors: surface #18181b, divider (decorative) #343538, text #ffffff; 28px radius; padding 32px; 1px border
- **feature card**: colors: text #ffffff
- sections fade and rise 12px into view (200ms, staggered 60ms)
- every interactive element shows a 2px #fde533 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}, Plan{name, monthlyPrice, yearlyPrice, features[], highlighted}, 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 #fde533 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.
Verified contrast: body text on canvas #ffffff on #000000 = 21.0:1; body text on surface #ffffff on #18181b = 17.72:1; muted text on canvas #a8afb7 on #000000 = 9.48:1; muted text on surface #a8afb7 on #18181b = 8.0:1; primary action label on fill #000000 on #fde533 = 16.43:1; link text on canvas #fde533 on #000000 = 16.43:1; focus ring on canvas #fde533 on #000000 = 16.43:1; focus ring on surface #fde533 on #18181b = 13.86:1; input border on canvas #63656a on #000000 = 3.6:1; accent icons and active marks on canvas #fde533 on #000000 = 16.43: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 (#fde533 fill, #000000 label) and use it once per view; secondary actions stay outlined or text-only.
- Use the yellow accent for small marks only (links, active states, icons), at most two or three times per screen.
- Buttons and chips are pills; cards keep their own radius so the two read differently.
- Limit headline sizes to the type scale; the 96px 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.