The interface follows the retro-terminal language of remote-pad (its live cousin, taken further, is radio.braquage.fun): pure black, hairline borders, monospace everywhere, one accent color, bracketed labels. The app should feel like a serious TUI that happens to render graphs, not a marketing site.
Base theme copied from remote-pad’s style.css. Start
from exactly this and extend only if forced to:
:root {
--font-mono: "JetBrains Mono", "Fira Code", ui-monospace, monospace;
--bg: #000000;
--fg: #e6e6e6;
--fg-dim: #808080;
--fg-faint: #4a4a4a;
--border: rgba(255, 255, 255, 0.18);
--border-strong: rgba(255, 255, 255, 0.4);
--accent: #6ee7a0; /* pick ONE accent; terminal green fits automata */
--danger: #e66;
}color: var(--bg); background: var(--fg)). See the key and
click-zone styles in remote-pad.[ OP ], [ SAVE ], [ ON ] /
[ OFF ]. Transparent background; border appears on
hover/active only.RUN_PANEL, ALPHABET,
SAVED_AUTOMATA. Chrome text is small (0.68–0.85rem) with
letter-spacing (0.03em+).--danger) only for
destructive/release actions.| Surface | Treatment |
|---|---|
| Top bar | Tabs EDITOR / OPS / REGEX / SAVED; active tab gets the
hairline border; per-section tutorial lightbulb (amber, text
presentation; see Tutorials) |
| Editor canvas | xyflow nodes: --border strokes, selected =
--border-strong or invert; accepting states get a
double border (echoes peripheries=2 in the DOT
output); initial state marked with an arrow glyph |
| Run panel | Trace as a TUI list: > a → {q0, q1} lines, active
states in --accent; final step shows
[ ACCEPTED ] / [ REJECTED ] |
| Status bar (bottom) | Mode (DFA/NFA from the determinism check),
alphabet size, state/transition counts, dim hints; remote-pad’s
statusbar, plus the radio’s pulse-dot for “dirty/unsaved” |
| Empty states | Small ASCII automaton + one bracketed call to action |
| Modals | Bracketed title + [ X ] CLOSE, like the radio’s about
modal |
Every major section (regex, editor, OPS, grammar, machines) has a tutorial trigger: a lightbulb glyph in the top bar, in text presentation (the emoji variant is wrong for a TUI), tinted amber, the one sanctioned second accent, marking “the sensei is here”.
Clicking it docks the sensei panel next to the live UI (the dojo
Scene, not a new component family) and he walks through the section:
theory first, then where things live in this UI, then worked
examples. Optional spotlight dimming darkens everything except the
control under discussion; [ SHOW ME ] steps drive the real
inputs and buttons in front of you, in the same bracketed-button
language as everything else.
The pattern is strictly opt-in per click and
stateless: no first-run tour, no persistence, nothing to
dismiss forever. Closing the panel returns the UI to exactly what it
was. Tutorials are data, not code: steps live in
web/src/lib/tutorial/ as typed step lists with inline
English and Spanish content (the dojo’s lines.ts is the
precedent).
The sensei is drawn, not typed: web/src/lib/choi/choi.ts
builds him from generated brush strokes, so one drawing serves every
size.
Q in a hat, a state. Two eyebrow strands spill
past the outline. He hovers: no legs, no arms.calm, stern,
surprised, awake (the one accent: mint eyes)
and proud (flat eyes, chin up, smirk).Splash.svelte): he drifts
in a sampan under an accepting-state moon, refracted below the waterline
with a fixed paper grain (a WebGL pass; the plain scene without WebGL).
It covers the app only until the first api answer, however short that
is; any key skips it, and it is a still frame under reduced motion.bun scripts/favicon.ts.