Irishurst

A dark, precise and engineering-flavored visual system for a crypto and web3 product. Its look rests on light 300-weight display type up to 89px, tight display tracking (-0.035em) and a sparing chartreuse 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 Irishurst.

What makes it

• light 300-weight display type up to 89px
• tight display tracking (-0.035em)
• serif headlines over a sans-serif body
• monospace used for labels, metadata or code
• short uppercase labels with open tracking
• small 4px corners on controls
• one subtle shadow for raised elements
• gradient fields used as atmosphere, never behind body text

Colors

Precise, focused, nocturnal. A near-black ground, light 300-weight display type up to 89px and a sparing chartreuse accent set the tone.

• canvas#060606
• surface#1f1f1f
• text#ffffff
• muted text#8a8a8a
• divider (decorative), never behind text#3d3d3d
• input border#6a6a6a
• accent / primary action fill / link text / focus ring#c5ff4a
• primary action label#000000
• supporting accent (decorative), never behind text#597321

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

• Source Serif 4Headings
• Inter TightBody
• Roboto MonoFigures and code

Type scale

Corners and shadows

• tags: 2px
• cards: 0px
• buttons: 4px
• logo-tiles: 4px
• shadow-1: rgba(197, 255, 74, 0.45) 0px 0px 8px 0px

Spacing and imagery

comfortable density on a 4px base unit; container 1280px; section gap 80px-120px; card padding 32px-48px; element gap 16px-20px; radii tags 2px, cards 0px, buttons 4px, logo-tiles 4px; 1 shadow level

Photography, illustration, 3d renders, abstract gradients. 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. sticky 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. article or story cards with image, kicker, title and date
6. large framed product view on a tinted surface
7. row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
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 1280px centered container with 24px side padding (16px on mobile)
11. sections are separated by 80px-120px 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)
• article or story cards with image, kicker, title and date
• large framed product view on a tinted surface
• row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
• metrics band with three or four large figures and captions

Components

• primary button: fill #c5ff4a, label #000000; 4px radius; padding 14px 24px; type 14px; soft shadow
• secondary button: transparent fill; label accent #c5ff4a; type 13px; uppercase with at least 0.05em tracking
• primary button (variant 2): fill #c5ff4a, label #000000; 4px radius; padding 14px 24px; 1px border; type 14px; uppercase with at least 0.05em tracking
• content card: colors: surface #1f1f1f, muted text #8a8a8a; 0px radius; padding 40px; 1px border; type 14px; no shadow
• content card (variant 2): colors: surface #1f1f1f, divider (decorative) #3d3d3d, accent #c5ff4a; 4px radius; padding 24px; 1px border; type 13px
• pill badge: colors: muted text #8a8a8a; type 12px/500; uppercase with at least 0.05em tracking
• hero block: colors: text #ffffff, canvas #060606
• announcement strip: colors: accent #c5ff4a
• pill badge (variant 2): colors: accent #c5ff4a; pill radius; padding 4px 10px; 1px border; type 12px; uppercase with at least 0.05em tracking
• top navigation bar: colors: primary action label #000000, surface #1f1f1f; 1px border; sticky

Interactions and states

• hover reveals a 1px accent outline; code and terminal lines type in once on first view
• every interactive element shows a 2px #c5ff4a 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 (#c5ff4a fill, #000000 label) and use it once per view; secondary actions stay outlined or text-only.
• Use the chartreuse accent for small marks only (links, active states, icons), at most two or three times per screen.
• Use the 4px control radius consistently; do not mix in pill shapes.
• Limit headline sizes to the type scale; the 89px display size appears once per page, in the hero.
• Keep gradients to backgrounds and decorative fields; they are never a button or text fill.
• 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 #c5ff4a 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.
• 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.
• The marketing site shows no account data and never asks for credentials, seed phrases or keys; sign-in links go to the separate app domain.

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 crypto and web3 product in the "Irishurst" style: dark, precise and engineering-flavored, with light 300-weight display type up to 89px, tight display tracking (-0.035em), serif headlines over a sans-serif body. Use invented copy and placeholder imagery throughout.

### Stack
Astro, TypeScript, Tailwind CSS, React islands with Radix primitives (tabs, accordion, dialog), Lucide icons, 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:
- sticky 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)
- article or story cards with image, kicker, title and date
- large framed product view on a tinted surface
- row of placeholder partner marks in a single muted tone (wraps to two rows on mobile)
- metrics band with three or four large figures and captions
- footer with grouped link columns, legal line and social icons
- content sits in a 1280px centered container with 24px side padding (16px on mobile)
- sections are separated by 80px-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: #060606;
  --color-surface: #1f1f1f;
  --color-text: #ffffff;
  --color-muted-text: #8a8a8a;
  --color-divider: #3d3d3d;
  --color-input-border: #6a6a6a;
  --color-accent: #c5ff4a;
  --color-primary-action-label: #000000;
  --color-supporting-accent: #597321;
  --text-12: 12px;
  --text-14: 14px;
  --text-16: 16px;
  --text-20: 20px;
  --text-32: 32px;
  --text-49: 49px;
  --text-72: 72px;
  --text-89: 89px;
  --radius-tags: 2px;
  --radius-cards: 0px;
  --radius-buttons: 4px;
  --radius-logo-tiles: 4px;
  --space-unit: 4px;
  --container: 1280px;
  --shadow-1: rgba(197, 255, 74, 0.45) 0px 0px 8px 0px;
}
```
Display Source Serif 4, body Inter Tight, mono Roboto Mono (Google Fonts, self-hosted, font-display: swap).
Type scale (size/weight/line-height tracking): 12px/400/1.2 0.024em, 14px/400/1.55, 16px/400/1.5, 20px/400/1.5 -0.010em, 32px/300/1.15 -0.013em, 49px/300/1.05 -0.020em, 72px/300/0.98 -0.025em, 89px/300/0.94 -0.035em.
Spacing: comfortable density on a 4px base unit; container 1280px; section gap 80px-120px; card padding 32px-48px; element gap 16px-20px; radii tags 2px, cards 0px, buttons 4px, logo-tiles 4px; 1 shadow level.
Signature moves: light 300-weight display type up to 89px; tight display tracking (-0.035em); serif headlines over a sans-serif body; monospace used for labels, metadata or code; short uppercase labels with open tracking; small 4px corners on controls; one subtle shadow for raised elements; gradient fields used as atmosphere, never behind body text.

### Components & interactions
- **primary button**: fill #c5ff4a, label #000000; 4px radius; padding 14px 24px; type 14px; soft shadow
- **secondary button**: transparent fill; label accent #c5ff4a; type 13px; uppercase with at least 0.05em tracking
- **primary button (variant 2)**: fill #c5ff4a, label #000000; 4px radius; padding 14px 24px; 1px border; type 14px; uppercase with at least 0.05em tracking
- **content card**: colors: surface #1f1f1f, muted text #8a8a8a; 0px radius; padding 40px; 1px border; type 14px; no shadow
- **content card (variant 2)**: colors: surface #1f1f1f, divider (decorative) #3d3d3d, accent #c5ff4a; 4px radius; padding 24px; 1px border; type 13px
- **pill badge**: colors: muted text #8a8a8a; type 12px/500; uppercase with at least 0.05em tracking
- **hero block**: colors: text #ffffff, canvas #060606
- **announcement strip**: colors: accent #c5ff4a
- **pill badge (variant 2)**: colors: accent #c5ff4a; pill radius; padding 4px 10px; 1px border; type 12px; uppercase with at least 0.05em tracking
- **top navigation bar**: colors: primary action label #000000, surface #1f1f1f; 1px border; sticky
- hover reveals a 1px accent outline; code and terminal lines type in once on first view
- every interactive element shows a 2px #c5ff4a 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}, Metric{value, label}, 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 #c5ff4a 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.
- 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 #ffffff on #060606 = 20.26:1; body text on surface #ffffff on #1f1f1f = 16.48:1; muted text on canvas #8a8a8a on #060606 = 5.87:1; muted text on surface #8a8a8a on #1f1f1f = 4.77:1; primary action label on fill #000000 on #c5ff4a = 17.78:1; link text on canvas #c5ff4a on #060606 = 17.15:1; focus ring on canvas #c5ff4a on #060606 = 17.15:1; focus ring on surface #c5ff4a on #1f1f1f = 13.95:1; input border on canvas #6a6a6a on #060606 = 3.75:1; accent icons and active marks on canvas #c5ff4a on #060606 = 17.15: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.
- The marketing site shows no account data and never asks for credentials, seed phrases or keys; sign-in links go to the separate app domain.

### 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 (#c5ff4a fill, #000000 label) and use it once per view; secondary actions stay outlined or text-only.
- Use the chartreuse accent for small marks only (links, active states, icons), at most two or three times per screen.
- Use the 4px control radius consistently; do not mix in pill shapes.
- Limit headline sizes to the type scale; the 89px display size appears once per page, in the hero.
- Keep gradients to backgrounds and decorative fields; they are never a button or text fill.
- 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.

Open the builderThe whole gallery