Emberwick

An airy, with gradient atmosphere light-theme style for a creative software product website. Its look rests on heavy 700-weight display type up to 72px, tight display tracking (-0.020em) and a sparing indigo accent on a 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 Emberwick.

What makes it

• heavy 700-weight display type up to 72px
• tight display tracking (-0.020em)
• monospace used for labels, metadata or code
• short uppercase labels with open tracking
• rounded 16px controls
• one subtle shadow for raised elements
• one indigo accent used sparingly
• gradient fields used as atmosphere, never behind body text

Colors

Optimistic, light, modern. A white ground, heavy 700-weight display type up to 72px and a sparing indigo accent set the tone.

• canvas / primary action label / text on band#ffffff
• surface#f6f6f6
• text#595959
• muted text#52525b
• divider (decorative) / input border / primary action fill / inverse band#000000
• accent / link text / focus ring#4d49fc

Every checked pair, measured again

Typefaces

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

Type scale

Corners and shadows

• content-cards: 0px
• floating-panels: 16px
• global-nav-buttons: 50px
• contextual-buttons: 8px
• shadow-1: rgba(0, 0, 0, 0.1) 0px 24px 70px 0px

Spacing and imagery

comfortable density on a 4px base unit; container 1440px; section gap 96px-120px; card padding 16px; element gap 24px; radii content-cards 0px, floating-panels 16px, global-nav-buttons 50px, contextual-buttons 8px; 1 shadow level

Photography, illustration, 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. centered hero: headline, one-line lede and a primary plus secondary action, visual below
3. alternating two-column text-and-visual blocks
4. metrics band with three or four large figures and captions
5. horizontal card rail with previous/next buttons and snap scrolling
6. feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
7. testimonial cards with quote, name and role
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 96px-120px of vertical space on desktop, roughly half that on mobile

Patterns

• hero
• alternating two-column text-and-visual blocks
• metrics band with three or four large figures and captions
• horizontal card rail with previous/next buttons and snap scrolling
• feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
• testimonial cards with quote, name and role

Components

• secondary button: follows the shared tokens
• content card: follows the shared tokens
• content card (variant 2): follows the shared tokens
• pill badge: colors: divider (decorative) #000000, canvas #ffffff; 50px radius; padding 8px 18px; type 16px
• pill badge (variant 2): colors: divider (decorative) #000000; 50px radius; padding 8px 18px; 1.5px border
• primary button: fill #000000, label #ffffff; 8px radius; padding 8px 16px

Interactions and states

• gradient fields drift slowly; paused on hover and under reduced motion
• every interactive element shows a 2px #4d49fc 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 (#000000 fill, #ffffff label) and use it once per view; secondary actions stay outlined or text-only.
• Use the indigo accent for small marks only (links, active states, icons), at most two or three times per screen.
• Keep the 16px control radius consistent across buttons, inputs and chips.
• Limit headline sizes to the type scale; the 72px display size appears once per page, in the hero.
• Keep gradients to backgrounds and decorative fields; they are never a button or text fill.
• 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 #4d49fc 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.

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 light-theme marketing site for a fictional creative software product in the "Emberwick" style: airy, with gradient atmosphere, with heavy 700-weight display type up to 72px, tight display tracking (-0.020em), monospace used for labels, metadata or code. 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
- metrics band with three or four large figures and captions
- horizontal card rail with previous/next buttons and snap scrolling
- feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
- testimonial cards with quote, name and role
- 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 96px-120px 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: #ffffff;
  --color-surface: #f6f6f6;
  --color-text: #595959;
  --color-muted-text: #52525b;
  --color-divider: #000000;
  --color-accent: #4d49fc;
  --text-12: 12px;
  --text-16: 16px;
  --text-18: 18px;
  --text-24: 24px;
  --text-56: 56px;
  --text-72: 72px;
  --radius-content-cards: 0px;
  --radius-floating-panels: 16px;
  --radius-global-nav-buttons: 50px;
  --radius-contextual-buttons: 8px;
  --space-unit: 4px;
  --container: 1440px;
  --shadow-1: rgba(0, 0, 0, 0.1) 0px 24px 70px 0px;
}
```
Display Inter, body Inter, mono Roboto Mono (Google Fonts, self-hosted, font-display: swap).
Type scale (size/weight/line-height tracking): 12px/400/1.0 0.030em, 16px/400/1.4, 18px/400/1.4, 24px/400/1.3 -0.010em, 56px/700/1.1 -0.009em, 72px/700/1.0 -0.020em.
Spacing: comfortable density on a 4px base unit; container 1440px; section gap 96px-120px; card padding 16px; element gap 24px; radii content-cards 0px, floating-panels 16px, global-nav-buttons 50px, contextual-buttons 8px; 1 shadow level.
Signature moves: heavy 700-weight display type up to 72px; tight display tracking (-0.020em); monospace used for labels, metadata or code; short uppercase labels with open tracking; rounded 16px controls; one subtle shadow for raised elements; one indigo accent used sparingly; gradient fields used as atmosphere, never behind body text.

### Components & interactions
- **secondary button**: follows the shared tokens
- **content card**: follows the shared tokens
- **content card (variant 2)**: follows the shared tokens
- **pill badge**: colors: divider (decorative) #000000, canvas #ffffff; 50px radius; padding 8px 18px; type 16px
- **pill badge (variant 2)**: colors: divider (decorative) #000000; 50px radius; padding 8px 18px; 1.5px border
- **primary button**: fill #000000, label #ffffff; 8px radius; padding 8px 16px
- gradient fields drift slowly; paused on hover and under reduced motion
- every interactive element shows a 2px #4d49fc 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}, Testimonial{quote, name, role, avatarUrl}, 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 #4d49fc 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 #595959 on #ffffff = 7.0:1; body text on surface #595959 on #f6f6f6 = 6.48:1; muted text on canvas #52525b on #ffffff = 7.73:1; muted text on surface #52525b on #f6f6f6 = 7.15:1; primary action label on fill #ffffff on #000000 = 21.0:1; link text on canvas #4d49fc on #ffffff = 5.72:1; focus ring on canvas #4d49fc on #ffffff = 5.72:1; focus ring on surface #4d49fc on #f6f6f6 = 5.29:1; input border on canvas #000000 on #ffffff = 21.0:1; accent icons and active marks on canvas #4d49fc on #ffffff = 5.72:1; text on inverse band #ffffff on #000000 = 21.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.

### 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 indigo accent for small marks only (links, active states, icons), at most two or three times per screen.
- Keep the 16px control radius consistent across buttons, inputs and chips.
- Limit headline sizes to the type scale; the 72px display size appears once per page, in the hero.
- Keep gradients to backgrounds and decorative fields; they are never a button or text fill.
- 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