Linear — Dark Gradient SaaS

Dark SaaSVisit sitelinear.app

Precision-engineered dark UI with a single electric accent and hairline structure.

Linear — Dark Gradient SaaS — captured interface — Page excerpt · scroll inside to explore

Source capture · 2026-09-05Open full image ↗

Motion

Design notes

Mood: Engineered, calm, premium-technical. Feels like a tool built by people who care about craft.
Colors: Near-black base (#08090A / #0E0F11), cool neutral grays for text, a single electric-violet-to-blue accent used sparingly. Almost no pure white; brightest text is a soft #F7F8F8.
Type: Inter (or similar geometric grotesque), tight letter-spacing, heavy weights on the hero headline, generous line-height in body. Sizes step down cleanly; no decorative fonts.
Layout: Centered hero with a short punchy headline + one-line subhead + single primary CTA. Thin vertical rhythm, sections separated by faint 1px borders, feature blocks in bordered cards or a subtle grid.
Motion: Slow fade-up on scroll, gentle gradient drift in the background, cursor-reactive glow behind the hero. Nothing bouncy; everything eased and quiet.
Texture: Fine noise/grain overlay, 1px hairline borders (rgba white ~8%), soft radial glows bleeding from behind headings and cards.
Imagery: Generate: soft radial violet-to-blue glow orbs, a fine noise/grain overlay (PNG, low opacity), and dark app/dashboard UI mockups. Keep imagery dark, minimal, and glow-driven. Tool: kie-ai Flux or Seedream for glows/textures; GPT-Image for stylized UI panels.
Don't: No hard drop shadows, no bright pure-white backgrounds, no rounded-cartoon shapes, no saturated multi-color palettes.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Linear — Dark Gradient SaaS
Source: https://linear.app
Swipefile reference: https://swipefile.design/ref/linear-dark/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- mood: Engineered, calm, premium-technical. Feels like a tool built by people who care about craft.
- colors: Near-black base (#08090A / #0E0F11), cool neutral grays for text, a single electric-violet-to-blue accent used sparingly. Almost no pure white; brightest text is a soft #F7F8F8.
- typography: Inter (or similar geometric grotesque), tight letter-spacing, heavy weights on the hero headline, generous line-height in body. Sizes step down cleanly; no decorative fonts.
- layout: Centered hero with a short punchy headline + one-line subhead + single primary CTA. Thin vertical rhythm, sections separated by faint 1px borders, feature blocks in bordered cards or a subtle grid.
- motion: Slow fade-up on scroll, gentle gradient drift in the background, cursor-reactive glow behind the hero. Nothing bouncy; everything eased and quiet.
- texture: Fine noise/grain overlay, 1px hairline borders (rgba white ~8%), soft radial glows bleeding from behind headings and cards.
- dont: No hard drop shadows, no bright pure-white backgrounds, no rounded-cartoon shapes, no saturated multi-color palettes.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Linear — Dark Gradient SaaS

Make it your own

Keep exploring