cyberdeck-setuplisted

# Cyberdeck Setup Builds a cohesive, matrix-green/cyber-purple terminal environment across every tool a Linux developer touches daily — one shared palette, not eleven mismatched ones. This skill was reverse-engineered from a real end-to-end session, including the bugs hit along the way. Follow it as a runbook, not a suggestion list — several steps exist specifically because the naive approach silently breaks (see **Known gotchas** below). ## Ground rules - **Linux + bash only.** If `uname -s` isn't `Linux`, or the user's shell isn't bash (check `$SHELL`), stop and tell the user this skill doesn't cover their setup yet. - **Never run `sudo` yourself.** This environment usually has no interactive TTY for a password prompt, and even when it does, silently escalating is not this skill's call to make. Every install in this skill uses a **no-sudo, user-local** pattern (`~/.local/bin`, `~/.local/share/fonts`, tarball/binary downloads) specifically so root is never required. If a step genuinely needs `apt`/`dnf`/etc., say so and hand the user the exact command — don't run it for them. - **Idempotent and non-destructive.** Before writing to a dotfile that might already have user content (`~/.bashrc`, `~/.bash_aliases`, `~/.gitconfig`), read it first. Never blind-overwrite. Append with a clear marker comment, or merge structured files (JSON/TOML) programmatically instead of clobbering. - **Verify every step**, don't just assume success. Run `--version`, config-val