Swiss grid

A starting style vibld wrote for agency, portfolio, studio, editorial sites. Strict 12-column grid, oversized type, black and white with one spot color, numbers as section markers.

Build in this styleRead the build prompt

In the builder, open Gallery under the message and search for Swiss grid.

What makes it

• strict 12-column grid with visible alignment
• oversized tight headlines
• black and white with one orange spot color
• numbers as section markers

Colors

Strict 12-column grid, oversized type, black and white with one spot color, numbers as section markers.

• canvas#ffffff
• surface#f2f2f2
• text / primary action label / link text#000000
• muted text#6e6e6e
• accent / primary action fill / focus ring#ff3b00
• divider (decorative), never behind text#e0e0e0

Every checked pair, measured again

Typefaces

modular scale 1.5; no text below 12px

• Inter TightHeadings
• InterBody

Type scale

Corners and shadows

• cards: 0px
• images: 0px
• inputs: 0px
• buttons: 0px

No shadows: depth comes from surfaces and lines.

Spacing and imagery

airy density on a 4px base unit; container 1200px; section gap 112px; radius 0px

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

Layout

1. navigation: Text-only links in a single row, current page underlined.
2. hero: Headline set at 9 to 12vw across the full grid, small meta text in a top-right column, no hero image.
3. social proof: Client list as a text index with years, no logos.
4. pricing: Plain table with hairline rules, prices right-aligned.
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 112px of vertical space on desktop, roughly half that on mobile

Patterns

• navigation
• hero
• social proof
• pricing

Components

• primary button: fill #ff3b00, label #000000; 0px radius; padding 14px 24px; type 16px/600
• card: surface fill; 0px radius; padding 24px

Interactions and states

• links underline on hover
• every interactive element shows a 2px #ff3b00 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 (#ff3b00 fill, #000000 label) and use it once per view.
• The navigation follows its rule: Text-only links in a single row, current page underlined.
• The hero follows its rule: Headline set at 9 to 12vw across the full grid, small meta text in a top-right column, no hero image.
• The social proof follows its rule: Client list as a text index with years, no logos.
• The pricing follows its rule: Plain table with hairline rules, prices right-aligned.
• Avoid shadows.
• Avoid rounded corners.
• Avoid icons as decoration.
• 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 #ff3b00 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 light-theme site in the "Swiss grid" starting style: Strict 12-column grid, oversized type, black and white with one spot color, numbers as section markers. 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: Text-only links in a single row, current page underlined.
- hero: Headline set at 9 to 12vw across the full grid, small meta text in a top-right column, no hero image.
- social proof: Client list as a text index with years, no logos.
- pricing: Plain table with hairline rules, prices right-aligned.
- 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 112px 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: #ffffff;
  --color-surface: #f2f2f2;
  --color-text: #000000;
  --color-muted-text: #6e6e6e;
  --color-accent: #ff3b00;
  --color-divider: #e0e0e0;
  --text-12: 12px;
  --text-14: 14px;
  --text-16: 16px;
  --text-24: 24px;
  --text-36: 36px;
  --text-54: 54px;
  --text-81: 81px;
  --text-122: 122px;
  --radius: 0px;
  --space-unit: 4px;
  --container: 1200px;
}
```
Fonts: display Inter Tight, body Inter (Google Fonts, self-hosted).
Type scale (size/weight/line-height tracking): 12px/400/1.5, 14px/400/1.5, 16px/400/1.5, 24px/500/1.4, 36px/700/1.18 -0.020em, 54px/700/1.12 -0.020em, 81px/700/1.06 -0.020em, 122px/700/1 -0.020em.
Spacing: airy density on a 4px base unit; container 1200px; section gap 112px; one corner radius, 0px, on cards, images, inputs and buttons.
Signature moves: strict 12-column grid with visible alignment; oversized tight headlines; black and white with one orange spot color; numbers as section markers.

### Components & interactions
- **primary button**: fill #ff3b00, label #000000; 0px radius; padding 14px 24px; type 16px/600
- **secondary button**: transparent fill, 1px border in the text color, 0px radius
- **card**: surface fill, 0px radius, padding 24px, no shadow
- links underline on hover
- every interactive element shows a 2px #ff3b00 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 #ff3b00 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 #000000 on #ffffff = 21:1; body text on surface #000000 on #f2f2f2 = 18.76:1; muted text on canvas #6e6e6e on #ffffff = 5.1:1; muted text on surface #6e6e6e on #f2f2f2 = 4.55:1; primary action label on fill #000000 on #ff3b00 = 5.88:1; link text on canvas #000000 on #ffffff = 21:1; focus ring on canvas #ff3b00 on #ffffff = 3.57:1; focus ring on surface #ff3b00 on #f2f2f2 = 3.19:1; accent marks on canvas #ff3b00 on #ffffff = 3.57: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 (#ff3b00 fill, #000000 label) and use it once per view.
- The navigation follows its rule: Text-only links in a single row, current page underlined.
- The hero follows its rule: Headline set at 9 to 12vw across the full grid, small meta text in a top-right column, no hero image.
- The social proof follows its rule: Client list as a text index with years, no logos.
- The pricing follows its rule: Plain table with hairline rules, prices right-aligned.
- Avoid shadows.
- Avoid rounded corners.
- Avoid icons as decoration.
- 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