Preview the prompt +
# Build brief — an original marketing website in the taste of Peira Network
> Reference: https://www.peira.network · UIDiscovery: https://uidiscovery.com/sites/peira-network · captured 2026-09-23 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/peira-network/full.png) · [scroll video](https://uidiscovery.com/media/captures/peira-network/preview.mp4)
## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Peira Network — same structure, rhythm and polish, entirely new identity and content.
## 2. Originality rules
- Build an ORIGINAL design for the user's own brand in the same *taste* as Peira Network: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Peira Network's logo, name, product imagery, illustrations, icons, screenshots or copy. Write new copy for the user's product.
- If the user hasn't said what their product is, ask first (or use clearly marked placeholders like [Brand], [Product], [Audience]).
- Reference screenshots are for looking at, not for embedding or tracing.
## 3. The taste, in short
- Peira Network (peira.network): Crypto & Web3 marketing website, dark, colorful.
- 0 sections: .
- Spacing: short, dense bands (median section ≈0px).
- Type: one family (Robit). Imagery: mostly typography with little or no imagery.
## 4. Page structure (top to bottom)
Inner pages also captured (Sign up, Contact, Security): https://uidiscovery.com/sites/peira-network?view=pages
## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#faf6f6` | page background | — |
| foreground | `#242424` | body text, headings | 14.5:1 |
| accent | `#ec411a` | primary buttons, links, highlights — sparingly | 3.7:1 (large text / UI only) |
| surface | `#ffffff` | cards, inputs, alternate bands | text on it 15.5:1 |
| muted | `#162b35` | secondary text, borders | 13.7:1 |
Captured palette: `#faf6f6` `#242424` `#162b35` `#ec411a` `#ffffff`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (dark, warm) and proportions; swap the accent for the user's brand colour.
### Tokens
```css
:root {
--background: #faf6f6;
--foreground: #242424;
--accent: #ec411a;
--surface: #ffffff;
--muted: #162b35;
--font-heading: "Inter", ui-sans-serif, system-ui, sans-serif;
--font-body: "Inter", ui-sans-serif, system-ui, sans-serif;
--radius: 12px; /* calibrate from the screenshot */
}
/* Tailwind v4 — in globals.css after @import "tailwindcss"; */
@theme {
--color-background: var(--background);
--color-foreground: var(--foreground);
--color-accent: var(--accent);
--color-surface: var(--surface);
--color-muted: var(--muted);
--font-heading: var(--font-heading);
--font-sans: var(--font-body);
}
```
### Typography
- Headings: **Inter** (Google Fonts) — reference uses Robit. “Robit” is likely a custom or licensed face. Inter is a neutral stand-in — pick a closer free match by eye from the screenshot.
- Body: same family — a single-family system; create contrast with size and weight, not a second face.
- Scale (starting point, sizes weren't measured — calibrate against the 1440px screenshot): display clamp(2.5rem, 5vw, 4.25rem), h2 clamp(1.75rem, 3vw, 2.5rem), h3 1.25rem, body 1rem–1.125rem / 1.6, small 0.875rem. Headings: tight tracking (-0.02em), line-height 1.05–1.15.
### Spacing & rhythm
Use an 8px grid; calibrate section padding from the screenshots.
### Shape, depth & theme
On dark, separate layers with 1px borders at ~8–12% white and soft glows instead of drop shadows; confident colour blocks — let full-bleed colour bands and big shapes carry the personality. Read exact corner radius, border and shadow treatment from the screenshots. Dark-first; for a light mode swap background ↔ foreground, lighten the surface, keep the accent and re-check contrast.
## 6. Imagery plan
Best guess: mostly **typography with little or no imagery** (dark, warm, Crypto & Web3). Inferred from element counts, colours and industry — not from the pixels — so open the linked screenshots and match the real style before sourcing anything.
- **Licences:** Unsplash and Pexels images are free for commercial use under their own licences; Pixabay under the Pixabay Content License. Check each image's page before use, credit the photographer when asked (good practice anyway), and skip images showing logos, trademarks, branded products or identifiable people without a release.
- **AI generation:** the prompts work with any image model (GPT Image, Imagen, Flux, Midjourney, Firefly, SDXL…) — check its commercial-use terms. Never put the reference brand's name or “in the style of <brand>” in a prompt.
- **Never** download, trace or re-host the reference's own images, illustrations, product shots or logos.
## 7. Build steps
1. Confirm brand, product, audience and the primary action with the user.
2. Set up the tokens (CSS variables / Tailwind @theme) and load the fonts.
3. Build the sections in order, mobile-first, with each reference screenshot open.
4. Write original copy for every slot — match length and tone, never the words.
5. Source every image via the imagery plan (stock or generated); compress it and record credits.
6. Run the checklist at 390 / 768 / 1440px and fix what fails.
## 8. Acceptance checklist
- [ ] Responsive at 390px, 768px and 1440px — no horizontal scroll, tap targets ≥ 44px on mobile.
- [ ] Colour contrast WCAG AA: 4.5:1 body text, 3:1 large text and UI; visible focus states; full keyboard navigation.
- [ ] Semantic HTML: one <h1>, ordered headings, landmarks (header/nav/main/footer), labelled form fields, alt text on meaningful images.
- [ ] Performance: modern image formats with width/height set, lazy-load below the fold, ≤ 2 font families with font-display: swap, LCP < 2.5s.
- [ ] prefers-reduced-motion respected; animations under ~300ms and never blocking content.
- [ ] Originality: no copied logos, images, illustrations or copy from the reference; every image licensed or generated; credits recorded.
## 9. If you use Next.js + Tailwind
Paste the @theme block into globals.css, load fonts with next/font/google, make each section a server component in components/sections/, use next/image with explicit sizes, and keep client components for interactive bits only (menus, toggles, accordions).
---
More: tokens https://uidiscovery.com/api/v1/sites/peira-network/tokens · kit https://uidiscovery.com/api/v1/sites/peira-network/kit · MCP `get_design_brief({ slug: "peira-network" })`, `get_image_plan({ slug: "peira-network" })`. Cite the reference as https://uidiscovery.com/sites/peira-network.
