Vinecroft

A light, airy, with gradient atmosphere visual system for a software product. Its look rests on 400-weight display type up to 104px, tight display tracking (-0.030em) and a sparing blue 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 Vinecroft.

What makes it

• 400-weight display type up to 104px
• tight display tracking (-0.030em)
• rounded 50px controls
• large 20px card corners
• one subtle shadow for raised elements
• one blue accent used sparingly
• gradient fields used as atmosphere, never behind body text

Colors

Optimistic, light, modern. A white ground, 400-weight display type up to 104px and a sparing blue accent set the tone.

• canvas / primary action label#ffffff
• surface#f1f5f9
• text#000000
• muted text#52525b
• divider (decorative), never behind text#d0d0d0
• input border#8c8c8c
• accent / primary action fill / focus ring#166aea
• link text#1569e8
• supporting accent (decorative), never behind text#101585
• second supporting accent (decorative), never behind text#dff994

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

• InterHeadings
• InterBody

Type scale

Corners and shadows

• tags: 20px
• cards: 20px
• images: 8.9px
• buttons: 50px
• nav-pills: 50px
• buttons-alt: 20px
• cards-small: 8.9px
• shadow-1: rgba(0, 0, 0, 0.1) 0px -1px 0px 0px

Spacing and imagery

comfortable density on a 4px base unit; container 1200px; section gap 80px; card padding 24px; element gap 12px; radii tags 20px, cards 20px, images 8.9px, buttons 50px, nav-pills 50px, buttons-alt 20px; 1 shadow level

Photography, product screenshots, illustration, abstract gradients. 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. feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
5. horizontal card rail with previous/next buttons and snap scrolling
6. large framed product view on a tinted surface
7. metrics band with three or four large figures and captions
8. testimonial cards with quote, name and role
9. footer with grouped link columns, legal line and social icons
10. content sits in a 1200px centered container with 24px side padding (16px on mobile)
11. sections are separated by 80px of vertical space on desktop, roughly half that on mobile

Patterns

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

Components

• primary button: fill #166aea, label #ffffff; 50px radius; padding 12px
• primary button (variant 2): fill #166aea, label #ffffff; pill radius; type 16px
• secondary button: transparent fill; pill radius; 1px border
• secondary button (variant 2): transparent fill; 20px radius
• content card: 20px radius; soft shadow
• content card (variant 2): 8.9px radius
• top navigation bar: colors: canvas #ffffff
• text input: colors: canvas #ffffff, surface #f1f5f9, input border #8c8c8c; 12px radius; 1px border
• hero block: follows the shared tokens
• section heading: follows the shared tokens
• pill badge: pill radius

Interactions and states

• gradient fields drift slowly; paused on hover and under reduced motion
• every interactive element shows a 2px #166aea 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 (#166aea fill, #ffffff label) and use it once per view; secondary actions stay outlined or text-only.
• Use the blue accent for small marks only (links, active states, icons), at most two or three times per screen.
• Keep the 50px control radius consistent across buttons, inputs and chips.
• Limit headline sizes to the type scale; the 104px 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 #166aea 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.

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 software product in the "Vinecroft" style: airy, with gradient atmosphere, with 400-weight display type up to 104px, tight display tracking (-0.030em), rounded 50px controls. 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
- feature grid of icon, title and two-line description cells (3-4 columns desktop, 1 column mobile)
- horizontal card rail with previous/next buttons and snap scrolling
- large framed product view on a tinted surface
- metrics band with three or four large figures and captions
- testimonial cards with quote, name and role
- 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 80px 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: #f1f5f9;
  --color-text: #000000;
  --color-muted-text: #52525b;
  --color-divider: #d0d0d0;
  --color-input-border: #8c8c8c;
  --color-accent: #166aea;
  --color-link-text: #1569e8;
  --color-supporting-accent: #101585;
  --color-second-supporting-accent: #dff994;
  --text-13: 13px;
  --text-16: 16px;
  --text-21: 21px;
  --text-31: 31px;
  --text-48: 48px;
  --text-82: 82px;
  --text-104: 104px;
  --radius-tags: 20px;
  --radius-cards: 20px;
  --radius-images: 8.9px;
  --radius-buttons: 50px;
  --radius-nav-pills: 50px;
  --radius-buttons-alt: 20px;
  --radius-cards-small: 8.9px;
  --space-unit: 4px;
  --container: 1200px;
  --shadow-1: rgba(0, 0, 0, 0.1) 0px -1px 0px 0px;
}
```
Display Inter, body Inter (Google Fonts, self-hosted, font-display: swap).
Type scale (size/weight/line-height tracking): 13px/400/1.2, 16px/400/1.5, 21px/400/1.3 -0.010em, 31px/400/1.2 -0.020em, 48px/400/1.1 -0.020em, 82px/400/1.0 -0.030em, 104px/400/0.95 -0.030em.
Spacing: comfortable density on a 4px base unit; container 1200px; section gap 80px; card padding 24px; element gap 12px; radii tags 20px, cards 20px, images 8.9px, buttons 50px, nav-pills 50px, buttons-alt 20px; 1 shadow level.
Signature moves: 400-weight display type up to 104px; tight display tracking (-0.030em); rounded 50px controls; large 20px card corners; one subtle shadow for raised elements; one blue accent used sparingly; gradient fields used as atmosphere, never behind body text.

### Components & interactions
- **primary button**: fill #166aea, label #ffffff; 50px radius; padding 12px
- **primary button (variant 2)**: fill #166aea, label #ffffff; pill radius; type 16px
- **secondary button**: transparent fill; pill radius; 1px border
- **secondary button (variant 2)**: transparent fill; 20px radius
- **content card**: 20px radius; soft shadow
- **content card (variant 2)**: 8.9px radius
- **top navigation bar**: colors: canvas #ffffff
- **text input**: colors: canvas #ffffff, surface #f1f5f9, input border #8c8c8c; 12px radius; 1px border
- **hero block**: follows the shared tokens
- **section heading**: follows the shared tokens
- **pill badge**: pill radius
- gradient fields drift slowly; paused on hover and under reduced motion
- every interactive element shows a 2px #166aea 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}, 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 #166aea 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 #000000 on #ffffff = 21.0:1; body text on surface #000000 on #f1f5f9 = 19.17:1; muted text on canvas #52525b on #ffffff = 7.73:1; muted text on surface #52525b on #f1f5f9 = 7.06:1; primary action label on fill #ffffff on #166aea = 4.9:1; link text on canvas #1569e8 on #ffffff = 4.98:1; focus ring on canvas #166aea on #ffffff = 4.9:1; focus ring on surface #166aea on #f1f5f9 = 4.47:1; input border on canvas #8c8c8c on #ffffff = 3.36:1; accent icons and active marks on canvas #166aea on #ffffff = 4.9: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 (#166aea fill, #ffffff label) and use it once per view; secondary actions stay outlined or text-only.
- Use the blue accent for small marks only (links, active states, icons), at most two or three times per screen.
- Keep the 50px control radius consistent across buttons, inputs and chips.
- Limit headline sizes to the type scale; the 104px 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