# One-shot Prompt: Red-team Deck Terminal

Create a single-file interactive terminal and fake operating system simulating a clandestine "Red-team deck".

## Core Requirements

1. **Fiction & Theming**: 
   - A dark, high-contrast CRT-style hacking interface (neon red/amber on black) with scanlines, subtle flicker, and terminal distortion.
   - Boot sequence simulating memory checks and daemon loading.
   - The interface is split into multiple panes: a primary command shell, a packet trace map or network topology view, and a live event/log stream.

2. **File System & State**:
   - Simulated virtual filesystem (directories like `/sys`, `/logs`, `/targets/subnet_gamma`, etc.).
   - Commands must interact with this state (e.g., `cd`, `ls`, `cat`).

3. **Signature Commands**:
   - Standard: `help`, `clear`, `history`, `ls`, `cd`, `cat`, `date`, `whoami`.
   - Thematic:
     - `probe [target]`: Scans a target IP/host and returns open ports.
     - `spoof [mac]`: Changes the deck's reported MAC address.
     - `trace [ip]`: Traces a route and visualises nodes on the packet map pane.
     - `burn`: Deletes traces and resets the session in a visual reset.
     - `decrypt [file]`: Runs a visual decryption matrix effect on a fake locked file.

4. **UX & Polish**:
   - Keyboard-first interaction with command history (Up/Down arrows) and tab completion.
   - Mobile fallback (a dedicated virtual keyboard or input bar with quick-tap command suggestions).
   - "Live" feeling: the background logs pane should passively stream fake packet intercepts and system warnings.

5. **Technical Constraints**:
   - Must be a single `index.html` file containing all HTML, CSS, and JavaScript.
   - No external assets (images/audio) unless data URI. Font loading from Google Fonts (e.g., VT323, Share Tech Mono) is allowed.
   - No backend or server required. All state lives in memory or `sessionStorage`.