Dark technical

A starting style vibld wrote for devtools, developer, observability, security sites. Near-black canvas, monospace accents, thin 1px borders, one bright signal color, code or terminal as hero art.

Build in this styleRead the build prompt

In the builder, open Gallery under the message and search for Dark technical.

What makes it

• near-black canvas with 1px borders instead of shadows
• monospace labels and figures
• one bright teal signal color
• code or terminal as hero art

Colors

Near-black canvas, monospace accents, thin 1px borders, one bright signal color, code or terminal as hero art.

• canvas / primary action label#0b0d12
• surface#12151c
• text#e8eaf0
• muted text#8a90a2
• accent / primary action fill / link text / focus ring#5eead4
• divider (decorative), never behind text#2e3036

Every checked pair, measured again

Typefaces

modular scale 1.25; no text below 12px

• Space GroteskHeadings
• InterBody
• Roboto MonoFigures and code

Type scale

Corners and shadows

• cards: 6px
• images: 6px
• inputs: 6px
• buttons: 6px

No shadows: depth comes from surfaces and lines.

Spacing and imagery

comfortable density on a 4px base unit; container 1200px; section gap 80px; radius 6px

Placeholder or generated imagery only; partner marks are neutral placeholders.

Layout

1. navigation: Compact 56px bar, docs link prominent, changelog link with a "new" dot.
2. hero: Centered headline with a short email field and action in one row, a row of placeholder marks directly below, an animated diagram or terminal under that.
3. social proof: Placeholder marks in grayscale at 60% opacity, one single stat such as uptime.
4. pricing: Usage-based slider or per-unit table; plan cards in a bordered grid without shadows.
5. footer with grouped link columns and a legal line
6. content sits in a 1200px centered container with 24px side padding (16px on mobile)
7. sections are separated by 80px of vertical space on desktop, roughly half that on mobile

Patterns

• navigation
• hero
• social proof
• pricing

Components

• primary button: fill #5eead4, label #0b0d12; 6px radius; padding 14px 24px; type 16px/600
• card: surface fill; 6px radius; padding 24px

Interactions and states

• links underline on hover
• every interactive element shows a 2px #5eead4 focus ring with 2px offset
• all motion is disabled under prefers-reduced-motion
• hover, focus-visible, active and disabled states for every button style
• mobile menu open and closed states
• forms: inline validation, sending, success and retryable error

Guardrails

Experience

• Keep one primary action style (#5eead4 fill, #0b0d12 label) and use it once per view.
• The navigation follows its rule: Compact 56px bar, docs link prominent, changelog link with a "new" dot.
• The hero follows its rule: Centered headline with a short email field and action in one row, a row of placeholder marks directly below, an animated diagram or terminal under that.
• The social proof follows its rule: Placeholder marks in grayscale at 60% opacity, one single stat such as uptime.
• The pricing follows its rule: Usage-based slider or per-unit table; plan cards in a bordered grid without shadows.
• Avoid neon on every element.
• Avoid gray text under 4.5:1 contrast.
• Avoid glow effects on body copy.
• Every number, quote, rating and partner mark is a placeholder the owner replaces; never invent real customers, logos or results.

Accessibility

• Text, links, focus rings and input borders use only the verified pairs listed in contrast checks.
• Focus ring: 2px solid #5eead4 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 never carry text or the only signal of state.
• Respect prefers-reduced-motion; no autoplay video without a pause control.

Security

• Validate every form on the client and again on the server; reject unknown fields.
• 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 site in the "Dark technical" starting style: Near-black canvas, monospace accents, thin 1px borders, one bright signal color, code or terminal as hero art. Write all copy fresh for the product in the request.

### Stack
Use the stack the request and the project already have. Design tokens live as CSS variables mapped into the Tailwind theme.

### Pages & layout
Home page sections, in order:
- navigation: Compact 56px bar, docs link prominent, changelog link with a "new" dot.
- hero: Centered headline with a short email field and action in one row, a row of placeholder marks directly below, an animated diagram or terminal under that.
- social proof: Placeholder marks in grayscale at 60% opacity, one single stat such as uptime.
- pricing: Usage-based slider or per-unit table; plan cards in a bordered grid without shadows.
- footer with grouped link columns and a legal line
- 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
Leave out pricing when the product has none to show. Test at 375px, 768px and 1280px.

### Design system
```css
:root {
  --color-canvas: #0b0d12;
  --color-surface: #12151c;
  --color-text: #e8eaf0;
  --color-muted-text: #8a90a2;
  --color-accent: #5eead4;
  --color-divider: #2e3036;
  --text-12: 12px;
  --text-14: 14px;
  --text-16: 16px;
  --text-20: 20px;
  --text-25: 25px;
  --text-31: 31px;
  --text-39: 39px;
  --text-49: 49px;
  --radius: 6px;
  --space-unit: 4px;
  --container: 1200px;
}
```
Fonts: display Space Grotesk, body Inter, mono Roboto Mono (Google Fonts, self-hosted).
Type scale (size/weight/line-height tracking): 12px/400/1.5, 14px/400/1.5, 16px/400/1.5, 20px/500/1.4, 25px/600/1.18 -0.020em, 31px/600/1.12 -0.020em, 39px/600/1.06 -0.020em, 49px/600/1 -0.020em.
Spacing: comfortable density on a 4px base unit; container 1200px; section gap 80px; one corner radius, 6px, on cards, images, inputs and buttons.
Signature moves: near-black canvas with 1px borders instead of shadows; monospace labels and figures; one bright teal signal color; code or terminal as hero art.

### Components & interactions
- **primary button**: fill #5eead4, label #0b0d12; 6px radius; padding 14px 24px; type 16px/600
- **secondary button**: transparent fill, 1px border in the text color, 6px radius
- **card**: surface fill, 6px radius, padding 24px
- links underline on hover
- every interactive element shows a 2px #5eead4 focus ring with 2px offset
- navigation collapses to a menu sheet under 768px, trapping focus while open

### Data & state
Content comes from typed local data. Handle hover, focus-visible, active and disabled states for every button, the mobile menu open and closed, and form validation, sending, success and error.

### Accessibility
- Text, links, focus rings and input borders use only the verified pairs listed in contrast checks.
- Focus ring: 2px solid #5eead4 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 never carry text or the only signal of state.
- Respect prefers-reduced-motion; no autoplay video without a pause control.
Verified contrast: body text on canvas #e8eaf0 on #0b0d12 = 16.16:1; body text on surface #e8eaf0 on #12151c = 15.18:1; muted text on canvas #8a90a2 on #0b0d12 = 6.1:1; muted text on surface #8a90a2 on #12151c = 5.73:1; primary action label on fill #0b0d12 on #5eead4 = 13.14:1; link text on canvas #5eead4 on #0b0d12 = 13.14:1; focus ring on canvas #5eead4 on #0b0d12 = 13.14:1; focus ring on surface #5eead4 on #12151c = 12.35:1; accent marks on canvas #5eead4 on #0b0d12 = 13.14:1.

### Security
- Validate every form on the client and again on the server; reject unknown fields.
- Open external links with rel="noopener noreferrer" and never put secrets or API keys in client code.

### Performance & SEO
- Images with explicit width and height, lazy-loaded below the fold; preload the display font only.
- One h1 per page, a descriptive title and meta description.

### Guardrails
- Keep one primary action style (#5eead4 fill, #0b0d12 label) and use it once per view.
- The navigation follows its rule: Compact 56px bar, docs link prominent, changelog link with a "new" dot.
- The hero follows its rule: Centered headline with a short email field and action in one row, a row of placeholder marks directly below, an animated diagram or terminal under that.
- The social proof follows its rule: Placeholder marks in grayscale at 60% opacity, one single stat such as uptime.
- The pricing follows its rule: Usage-based slider or per-unit table; plan cards in a bordered grid without shadows.
- Avoid neon on every element.
- Avoid gray text under 4.5:1 contrast.
- Avoid glow effects on body copy.
- Every number, quote, rating and partner mark is a placeholder the owner replaces; never invent real customers, logos or results.

Open the builderThe whole gallery