Prompt 898 words Copy
# Design from Reference: Unabyss Landing Page
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.
## Reference
- **Product:** Unabyss
- **Category:** Landing Page
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/57fb11c53e3e43a149b9-1600.webp)
- **Source:** https://unabyss.com/
Analyze the attached screenshot first. If no image is attached, open the screenshot link; if neither is accessible, ask for it rather than guessing.
## Visual Design Context
## Unabyss — shared visual language
- **Theme**: dark-only marketing site. Near-black warm background (#191817), cards one step lighter (~#1F1E1C) with 1px hairline borders (white at ~8% opacity) and 16–20px radii.
- **Typography**: Lexend throughout. Headlines 600 weight, ~60px on desktop, tight tracking; a two-line hero where the second line drops to a muted grey (~#8A8784) for contrast. Body copy 16–17px, light grey, generous line height. Small uppercase labels with very wide letter spacing ("WORKS WITH", "BACKED BY"); wordmark set in spaced capitals.
- **Accent**: a restrained warm gold/amber (#E8B33A-ish) used for highlight strokes, glowing rings, pill outlines ("confidential", "You own it") and connector lines; a green status dot for "In sync".
- **Components**: pill-shaped floating nav bar with a separate pill logo chip; white solid pill CTAs with a ↗ arrow icon; dark rounded logo tiles for integrations (Claude, ChatGPT, Cursor, Gmail, Slack, Notion, GitHub…); tag chips; mini UI mock cards ("Your context", "Unabyss · MCP") built from bars and status labels rather than screenshots.
- **Layout**: centered hero, then bento grids of feature cards mixing a short heading, one-line copy and an illustrative widget; inline brand icons placed inside headlines.
- **Tone**: calm, technical, confident; short declarative headings, developer-friendly vocabulary (MCP, context, memory).
### Overall aesthetic
- **Style:** Long, cinematic dark landing page with prism-like gradient light leaks in demo frames and a single warm amber accent.
- **Rhythm:** Every section repeats eyebrow label → H2 → bento or card grid, which keeps a very long page readable.
### Page composition
- **Hero:** Award badges, two-line H1 with brand icons embedded in the sentence (second line muted), short intro, white pill CTA, "Works with" ticker with an items-synced counter.
- **Demo:** Full-width rounded video frame with prism border light and a row of workflow thumbnails.
- **Argument:** Two-step Claude setup with the real connector card; "Two gaps" cards; before/after chat mockups with the "With Unabyss" side glowing yellow; three-step how-it-works; stats row; "A context you own" bento.
- **Closing:** Persona bento, three pricing cards with deep-sea photo headers and a monthly/annual toggle, Claude CTA, FAQ accordion, three blog cards, 4-column footer.
### Typography
- **Families:** Lexend everywhere, JetBrains Mono for timers and small technical labels.
- **Scale:** H1 60px/600 (-0.72px), H2 48px/600, card titles 15px/500, body 16px/300 at 27px line height, tiny uppercase eyebrows.
### Colors & surfaces
- **Backgrounds:** #0F0F0F and #191817, cards #1E1E1E/#262624 with hairline borders.
- **Text:** #FFFFFF, muted #6F6D67, pale amber #FEF3C7 for highlights.
- **Accent:** Amber/yellow for the big stat, highlighted plan and glow outlines; orange only on the Claude connector card.
### Components
- **Buttons:** White pill CTAs (36px, 12px/500 black text) with a ↗ icon.
- **Cards:** 16–24px radii, inline mini-UI widgets (sync status, tags, MCP diagram), chat-window mockups, pricing cards with check lists, accordion rows.
### Responsive
- **Mobile:** All grids collapse to one column; the hero headline wraps over several lines with icons kept inline; pricing cards stack with the Max plan first in emphasis.
### Adaptation guidance
- **Reuse:** The inline-icon headline with a dimmed second line suits any integration product; keep one accent color and let the eyebrow/H2/bento rhythm carry the page.
## Content
**Instructions:**
Generate realistic example content that fits the selected design reference.
Create appropriate headlines, descriptions, labels, buttons, and supporting copy based on the type of interface being designed.
If a product or business description is provided, use it to guide the content.
Otherwise, invent a plausible fictional SaaS product appropriate for the reference.
Keep the content concise, coherent, and visually balanced.
Do not present fictional statistics, customer names, or testimonials as verified facts.
## Design Direction
**Instructions:**
Use the reference screenshot as the main source of visual inspiration rather than a strict layout template.
Preserve its most distinctive design characteristics, such as typography, visual rhythm, color relationships, component treatments, and overall aesthetic.
Feel free to modify section arrangements, proportions, spacing, and individual components to better suit my content.
Introduce original design decisions where they improve usability, composition, or brand consistency.
The result should clearly reflect the reference's visual language without looking like a direct reproduction.
Follow the visual identity of the reference design.
Use its typography, color palette, component styling, and overall aesthetic as the primary design direction.
Do not introduce an unrelated visual identity.
## Output
**Instructions:**
Generate a high-fidelity visual mockup of the requested interface.
Present the design as a polished, realistic website or product UI screenshot.
Prioritize visual composition, typography, spacing, colors, alignment, and component details.
Use the available image-generation or visual-design capabilities.
Do not replace the mockup with source code, a written design specification, or a textual description.
If direct visual generation is unavailable, clearly explain the limitation.
## Constraints
- Use the actual screenshot as the primary visual reference.
- Preserve essential messaging and factual accuracy.
- Prioritize visual quality and consistency.
- Do not invent unsupported product claims.
- Adapt structure and copy length for visual balance. Reference image Attach it to your message: assistants can’t open image links. Open in ChatGPT ↗ Open in Claude ↗
Build it in Lovable ↗ v0 ↗ Figma Make ↗
Opening a tool copies the screenshot so you can paste it with your prompt.
SaaSFrame
