$ want_this_look

Build me a complete, responsive business website in the TERMINAL / CLI style — the command-line aesthetic of a green-phosphor CRT, WarGames, and "type to navigate" dev sites: monospace type, glowing green text on near-black, a blinking cursor, ASCII box-drawing, and a `$` prompt waiting for a command. Where other styles add decoration, this one subtracts it — text in, text out, zero ornament. The reduction IS the argument: it reads as competence and craft. Combine this style seed with my brief below. If I don't give you the details, invent a plausible business that suits this austere, technical, credible look — a security firm, a dev-tools startup, a self-hosting/homelab service, an indie CLI product — and build a full, real demo for it, not a placeholder. This style is deliberately tight — the phosphor-on-black palette and monospace type are the style and stay fixed. What varies is the SESSION FRAMING, the LAYOUT, and how far you push the fake-shell conceit. Pick an approach that fits my business and COMMIT to it across the whole site. ── INVARIANTS (never break these — they define the style) ── • MONOSPACE everything — a single fixed-width typeface for all text (JetBrains Mono, IBM Plex Mono, Space Mono, or similar via Google Fonts). No proportional, serif, or handwritten type, anywhere. The screen should read like a grid of character cells. • Phosphor-on-black palette: a near-black, slightly green-tinted background (e.g. #0C0F0C), glowing green foreground text (e.g. #33FF66), a hotter bright green for prompts/cursors/emphasis (e.g. #9CFF2E), and a dimmed green for secondary text and hairline borders (e.g. #1F8A3B). Color exists for legibility, not decoration — do NOT introduce a rainbow of hues; that breaks the illusion instantly. • Command-and-response framing: content is presented as input and output — a `$` (or custom) prompt, a typed command, a printed result. The interface behaves like a real shell waiting for the next instruction. Navigation can read as typed commands. • ASCII & cursors instead of icons and chrome: box-drawing characters (┌─┐│└┘) for panels and dividers, ASCII art for emphasis, and a blinking block or underscore cursor. Thin 1px hairline dividers only — terminals never round corners or cast shadows. • Motion is "type": text appears character by character as if printed, screens scroll like real output, cursors blink. Never ease, slide, or float like a modern UI. Honor prefers-reduced-motion (skip the typing, show the finished text), and keep ALL content visible without JavaScript — never leave a section stuck mid-type or invisible. • CONTRAST (WCAG 2.2 AA, non-negotiable): green-on-near-black clears AA (and usually AAA) easily — keep it that way. Body green ≥4.5:1 on the black; keep the dimmed "muted" green above 4.5:1 too (don't let secondary text fade below threshold). Never put green text on a light panel, and never stack two similar greens where one is text on the other as a fill. ── VARIABLES (choose an approach that fits my business, then commit) ── • PHOSPHOR COLOR — the one accepted variant: classic P31 GREEN (default) or P3 AMBER (a warm orange-amber foreground on the same near-black, the "easier on the eyes" 1980s terminal). Pick ONE and use it everywhere; do not mix green and amber. Everything else about the palette stays the same. • SESSION FRAMING — decide the conceit and commit: a literal fake shell session where each section is a command and its output; a `man`-page / documentation layout; a `git log` / changelog scroll; or a boot-sequence-into-content open. Choose a custom prompt string that fits (e.g. `visitor@business:~$`). • LAYOUT — a single full-width scrolling session; a two-pane split (command list / output); or ASCII box-drawn panels tiled on a grid. Also settle your own cursor style (block vs underscore), typing speed, and how heavily you lean on ASCII art. ── MEDIA MODEL (character cells, not stock photography) ── Build visuals from CHARACTERS — ASCII art, box-drawing panels, typed tables, `ls`-style listings, progress bars made of block characters, sparkline-style figures in text. This style is near-imageless by nature. Where the business genuinely needs a real photo (a product, the team), keep it rare and frame it plainly inside a box-drawn/hairline border with a monospace caption — never full-bleed, never rounded, never shadowed. Generate ASCII marks and output appropriate to MY business, not a reuse of any demo. WHAT THIS SITE MUST ACHIEVE (business goal): Make it instantly clear who this business helps and what it offers; explain the value plainly and precisely; reduce a first-time visitor's risk with real proof (results, credentials, client names, guarantees — whatever is true); and drive one clear next step — an enquiry, a signup, a quote, a call — framed naturally as a command or a printed CTA line. Let the business and its brief decide which sections serve that goal, include exactly those in a sensible order, and build each one fully. BUILD REQUIREMENTS — ship a complete, usable site, not a hero mock: • Real information architecture driven by MY business and goal — whatever sections move a stranger toward acting, each with one clear job, in an order that builds understanding then trust then action. Include working navigation (typed-command or plain links) and a footer that reads like a final log line or prompt. • Don't be lazy with any section: each carries real content depth (never a title plus one thin line), proper internal hierarchy expressed in the command/output rhythm, and the full terminal treatment. If a section only serves the style, cut it; if a section serves the goal but feels thin, flesh it out. • Real, tailored copy for MY business — precise, confident, and plainspoken, like good CLI output and man-page prose. Never lorem. • Fully responsive and accessible: semantic landmarks under the shell veneer, alt text on any real image, real selectable text (not images of text), and the CONTRAST invariant on EVERY section. On mobile, keep monospace and the character grid; let long lines wrap or scroll within a panel rather than breaking the layout. • Apply the chosen phosphor color, framing, and layout to EVERY section, not just the hero.

Best for AI website builders — Lovable, v0, Bolt

Restyle my existing site into the TERMINAL / CLI look — the command-line aesthetic of a green-phosphor CRT, WarGames, and "type to navigate" dev sites: monospace type, glowing green text on near-black, a blinking cursor, ASCII box-drawing, and a `$` prompt. Keep ALL of my current content, copy, pages, and structure exactly as they are; change only the visual language so everything reads like output printed to a shell. Do not invent new pages, remove sections, or rewrite my words. This style's palette and type are the style, so they don't bend to a brand — set the whole site in the phosphor-on-black scheme below rather than carrying my brand hues into it. The only brand-level choice is green vs amber. ── INVARIANTS (never break these) ── • Convert ALL text to a single MONOSPACE typeface (JetBrains Mono, IBM Plex Mono, Space Mono, or similar via Google Fonts). No proportional, serif, or handwritten type survives. • Recolor everything to the phosphor palette: near-black green-tinted background (e.g. #0C0F0C), glowing green foreground (e.g. #33FF66), hotter bright green for prompts/cursors/emphasis (e.g. #9CFF2E), dimmed green for secondary text and hairline borders (e.g. #1F8A3B). Strip every other hue — no rainbow of colors. • Reframe content as command-and-response where it fits: a `$` prompt, section headers as typed commands, bodies as printed output. Turn the nav into a typed-command or plain monospace menu. • Replace icons, rounded cards, and drop shadows with ASCII box-drawing (┌─┐│└┘) panels and thin 1px hairline dividers. No rounded corners, no shadows. • Motion becomes "type": text prints character by character, screens scroll like output, a cursor blinks. Remove every ease, slide, and float. Honor prefers-reduced-motion (show finished text) and never leave a section stuck mid-type or invisible; keep content visible without JavaScript. • Never: proportional/serif fonts, rounded corners, drop shadows, multiple competing colors, smooth easing transitions, light backgrounds. ── VARIABLE ── PHOSPHOR COLOR — pick ONE and use it everywhere: classic P31 GREEN (default) or P3 AMBER (warm orange-amber foreground on the same near-black). Do not mix the two. Wrap any existing image inside a box-drawn / hairline border with a monospace caption (squared corners, never rounded, never shadowed, never full-bleed); replace decorative gradients and icons with ASCII art, typed tables, or block-character bars. Keep real selectable text (never images of text). Keep it responsive and accessible — green-on-black clears WCAG 2.2 AA (≥4.5:1 body, ≥3:1 large) easily, so keep the dimmed "muted" green above 4.5:1 too and never put green text on a light panel. Restyle what already exists so every section reads as one continuous shell session — same content, new phosphor skin.

Paste alongside your existing site/code for an AI coding agent to apply

Design a single section in the TERMINAL / CLI style — the command-line look of a green-phosphor CRT and "type to navigate" dev sites: monospace type, glowing green text on near-black, a blinking cursor, ASCII box-drawing, and a `$` prompt. A low-commitment preview of the style, built richly for whatever section I ask for. Tell me in your own words, alongside this prompt, which section you want and the job it has to do — a boot-sequence hero, a pricing table, a services listing, a testimonial block, a signup CTA, a project directory listing. If I don't name one, build a boot-sequence hero for a plausible dev-tools or security business you invent. Whatever the section, build it fully and richly — don't be lazy: real, tailored copy, proper hierarchy, and depth, not a title plus one thin line. ── INVARIANTS ── • MONOSPACE everything (JetBrains Mono / IBM Plex Mono / Space Mono via Google Fonts) — no proportional or serif type. Phosphor palette: near-black green-tinted background (#0C0F0C), glowing green foreground (#33FF66), hotter bright green for prompt/cursor (#9CFF2E), dimmed green for secondary text and hairlines (#1F8A3B); no other hues. Command-and-response framing with a `$` prompt. ASCII box-drawing (┌─┐│└┘) and a blinking block/underscore cursor instead of icons; 1px hairlines, no rounded corners, no shadows. Motion is "type" — text prints character by character, cursor blinks; no easing or sliding; content visible without JavaScript, honoring prefers-reduced-motion. • Never: proportional/serif fonts, rounded corners, drop shadows, multiple competing colors, light backgrounds. ── VARIABLE (pick one, commit) ── PHOSPHOR COLOR — classic P31 GREEN (default) or P3 AMBER (warm orange-amber on the same near-black). Use one, never both. Also choose your prompt string, cursor style, and typing speed. Build the section from CHARACTERS — a `$` prompt and printed output, ASCII panels, typed tables, block-character bars. If it genuinely needs a real image, use a real placeholder <img> framed in a box-drawn / hairline border with a monospace caption — never a fake colored div standing in for a photo, never rounded, never full-bleed, never shadowed. Where the section's job calls for an action, print a clear CTA line or a command the visitor "runs". Make it responsive and accessible with real selectable text — green-on-black clears WCAG 2.2 AA (≥4.5:1 body, ≥3:1 large); keep muted green above threshold and never put green text on a light panel. Write real, tailored copy for the subject, not lorem.

Good for a focused first pass, or a chat-based assistant like ChatGPT/Claude