Departure Mono — Pixel Terminal Specimen

A font specimen as an airport diorama: everything set in the pixel mono itself, staged around boarding passes, receipts, departures boards, and cockpit HUD panels.

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

Design notes

Mood

Lo-fi sci-fi nostalgia played completely straight — early command-line interfaces and 90s pixel fonts wrapped in a deadpan airline fiction ('ATTN: PASSENGERS').

Colors

Light grey paper canvas (#E9E9E7) with near-black pixel ink. Sparse prop accents: highlighter green row/selection fills, kraft tan note cards, dark charcoal panels for boarding pass and access card. Nothing saturated beyond those.

Type

One monospaced pixel font at every size IS the design: giant chunky display headlines ('ATTN: PASSENGERS'), LCD-style boxed nav strip, tabular departures rows, tiny annotation captions listing the size and tracking used ('12PX -12PX TRACK'). No second typeface anywhere.

Layout

A staged diorama scroll: props scattered at angles (letter, boarding pass, receipt, luggage tag overlapping), full-width tabular sections with ruled columns, giant specimen headlines between scenes, and a cockpit-instrument footer with gauges, glyph lists, and a circular radar blueprint.

Motion

Terminal-flavored: text that types or flickers in, departures-board rows that flip/shuffle characters, blinking cursors and status LEDs, props easing in with a snap. Stepped, quantized movement — never smooth spring physics.

Texture

Flat paper background with fine blueprint line-work (circles, dashed guides) behind props. Props carry subtle paper shadow; screens are matte dark, not glossy. Everything reads as printed or displayed, never rendered 3D.

Imagery

Staged in-world props rendered as flat graphics, not photos: typed letters on white paper, a dark boarding pass with barcode, a diner receipt, a kraft-green luggage tag, blueprint line drawings of objects, an LCD departures board. Build these as HTML/SVG set in the pixel mono wherever possible; kie-ai Seedream only for paper-texture prop mockups. No photography of people or places.

Don't

No smooth antialiased display fonts, no photography, no gradients or glass, no bright brand colors, no rounded friendly UI. Never break the fiction — even the footer must stay in-world.

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 withAny AI toolCodexClaudeCursorChatGPTGeminiv0 / LovableI want toBuild a screenAudit my UIWrite a design brief

Tech stackUse the existing project stackReact / Next.jsAstroVue / NuxtSvelte / SvelteKitHTML / CSS / JavaScriptSwiftUIFlutter

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: Departure Mono — Pixel Terminal Specimen Source: https://departuremono.com Swipefile reference: https://swipefile.design/ref/departure-mono/ 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: Lo-fi sci-fi nostalgia played completely straight — early command-line interfaces and 90s pixel fonts wrapped in a deadpan airline fiction ('ATTN: PASSENGERS'). - colors: Light grey paper canvas (#E9E9E7) with near-black pixel ink. Sparse prop accents: highlighter green row/selection fills, kraft tan note cards, dark charcoal panels for boarding pass and access card. Nothing saturated beyond those. - typography: One monospaced pixel font at every size IS the design: giant chunky display headlines ('ATTN: PASSENGERS'), LCD-style boxed nav strip, tabular departures rows, tiny annotation captions listing the size and tracking used ('12PX -12PX TRACK'). No second typeface anywhere. - layout: A staged diorama scroll: props scattered at angles (letter, boarding pass, receipt, luggage tag overlapping), full-width tabular sections with ruled columns, giant specimen headlines between scenes, and a cockpit-instrument footer with gauges, glyph lists, and a circular radar blueprint. - motion: Terminal-flavored: text that types or flickers in, departures-board rows that flip/shuffle characters, blinking cursors and status LEDs, props easing in with a snap. Stepped, quantized movement — never smooth spring physics. - texture: Flat paper background with fine blueprint line-work (circles, dashed guides) behind props. Props carry subtle paper shadow; screens are matte dark, not glossy. Everything reads as printed or displayed, never rendered 3D. - dont: No smooth antialiased display fonts, no photography, no gradients or glass, no bright brand colors, no rounded friendly UI. Never break the fiction — even the footer must stay in-world. ## 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.

Copy promptDownload .md

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