boost ships a stunning Aurora living-glass web system — yet the CLI still
renders in plain 8-color ANSI: no gradient, no glass, no motion. This roadmap
closes that gap. Every item was found by driving the real CLI
(boost, doctor, search, list) and
grading its output against style/boost.css — then scored by
category, complexity, impact and wow-factor. Zero new dependencies;
NO_COLOR and non-TTY are always respected.
Proposed logged & triaged · Next queued · In progress being built · Shipped done.color, layout, motion, typography, ux, system, tooling.S a focused change · M a module-sized effort · L a multi-file refactor.High every session · Med real polish · Low finishing touch.zero-dependency, degrades on NO_COLOR / non-TTY, and targets Python ≥ 3.9.Bring the brand palette and gradient into the terminal — with graceful fallbacks.
output.pyThe whole CLI runs on eight legacy SGR codes (RED…CYAN) that don't match the brand at all — the front door paints section headers in generic [33m yellow. Add truecolor rgb() helpers mapping the exact web tokens: cyan #22d3ee, violet #a855f7, pink #f472d0, green #4ade80, yellow #facc15, plus --text/--text-3 greys. One map recolors everything.
core/output.py:15–38use_color() is binary — color or nothing. Add a tier ladder: truecolor (COLORTERM=truecolor/24bit) → 256 → 16 → none, so the Aurora tokens snap to the nearest available color instead of vanishing. Keep the existing NO_COLOR honor, add a BOOST_COLOR=always/auto/never override, and treat TERM=dumb as none.
core/output.py:26–38The brand is the cyan→violet→pink --grad. Interpolate it per-character across a string so headings, the boost wordmark and hero counts shimmer in the terminal exactly like the web hero. A pure-Python lerp over the three stops; falls back to a single accent color when truecolor is unavailable.
core/output.py · new gradient()Commands scatter out.c(x, out.YELLOW) and out.GREEN literally throughout the command layer, so a palette change means a repo-wide sweep. Introduce named roles — accent, brand, success, warn, danger, muted — resolved through the palette. Re-theming becomes a one-file edit, and intent reads clearly at every call site.
core/output.py · commands/*.pyWidth-aware output, glass panels, and results that never blow up the pane.
search: truncate & width-clamp resultsToday boost search is the worst screen in the app: a single result can dump a 2,000-character description with literal, unrendered \\n\\n escapes, while names are padded to a fixed 30 columns that waste half the row. Clamp each row to the live terminal width, collapse whitespace/escape artifacts, and ellipsize. This one fix turns a wall of noise into a scannable list.
commands/discovery.py · searchThe web system frames everything in rounded glass; the CLI frames nothing. Add rounded box-drawing primitives (╭─╮ │ ╰─╯) with dim --line borders and an optional title, mirroring the web .glass/.window surfaces. Reusable chrome for doctor, info, snapshot and success summaries.
core/output.py · new panel()Results are "ranked by heuristic relevance" but the ranking is invisible — every row looks equal. Render a tiny gradient relevance bar or score glyph per hit and visually separate curated from GitHub-wide matches, so the eye lands on the best result first.
commands/discovery.py · searchtable() is a naive ljust that ignores terminal width and left-aligns numeric columns. Make it width-aware (shrink the widest text column to fit), right-align counts with tabular figures, and add dim column separators — matching the web's font-variant-numeric: tabular-nums stat blocks.
core/output.py:71–83preview / catThe web guide renders skills inside a titled window with traffic-light dots (.window .dots). Give preview/cat the same treatment: a titled frame with the skill name in the bar, so a rendered SKILL.md in the terminal matches the screenshots on the site.
commands/info.py · preview/cattrending had the same overflow as searchGrading the un-touched commands surfaced a sibling of D05: boost trending piped raw catalog descriptions straight into table(), so a single 300-char description blew the table across the pane. Fixed by clipping each description through out.truncate() to the width left after the name/installs/last columns — the same helper the search fix introduced.
commands/discovery.py · cmd_trendingtable()out.table() backs 28 call sites, and several still overflow: taps pads the NAME column to the widest repo (K-Dense-AI/claude-scientific-skills = 44 cols) and then prints full URLs, so wide catalogs wrap. The durable fix is to make table() itself width-aware — shrink the widest text column to the terminal and right-align numeric columns — instead of truncating per-caller. Higher blast radius (28 callers, many exact-output tests), so it needs a careful, test-first pass.
core/output.py:table() · commands/taps.pyMake it feel snappy — spinners, progress, and instant first paint.
Network-bound commands — search (AI rank), tap clone, discover, index — currently freeze silently while they work. Add a lightweight braille-dot spinner (⠋⠙⠹⠸…) tinted with the Aurora accent, auto-suppressed on non-TTY and under NO_COLOR. The single biggest "feels fast" upgrade.
core/output.py · new spinner()Multi-item commands — reindex, update, sync, snapshot restore — give no sense of "how far in." Add a gradient-filled progress bar (N/total + ETA) for anything looping over a known count, so long operations read as intentional rather than hung.
core/output.py · new progress()search computes the full ranking, then prints the whole list at once — the terminal sits blank, then floods. Stream the top hits as they're scored so the first result paints almost immediately. Perceived latency drops even when total time is unchanged.
commands/discovery.py · searchok() prints a lone green check, then the command just ends. After install/uninstall, close with a small framed confirmation — what changed, where it landed, and the obvious next step (boost info <skill>) — so a completed action feels finished, not dropped.
core/output.py:41 · commands/pkg.pyThe screens users actually stare at — front door, doctor, list, info.
The boost home screen is the first thing everyone sees. Today the wordmark is plain bold and every group header is the same generic yellow. Paint the boost wordmark with the Aurora gradient and give each command group a colored bullet/glyph keyed to a brand hue — turning a flat list into a branded index.
commands/info.py · help rendererdoctor as a health dashboarddoctor is an undifferentiated wall of green checks — no hierarchy, no headline. Reframe it as a panel with a verdict line (● Healthy in green / ● Attention in amber), grouped checks, dim sub-detail, and severity color so a problem actually stands out instead of hiding among the ✓s.
commands/quality.py · doctorinfo skill identity cardinfo lists kv() pairs as flat dim labels. Promote it to a framed identity card: gradient skill name, status badges (installed / pinned / tap origin) styled like the web .badge pills, then the metadata — a real "detail view," not a key-value dump.
commands/info.py:177+list polish — chips & aligned countslist already uses a nice · agent separator; take it further. Color the agent names as small chips, right-align the count footer with tabular figures, and add a dim header rule so the table reads as a designed object rather than raw columns.
commands/info.py:130–131Empty and hint lines are ad-hoc — info's "no skills installed" hint is a hand-rolled DIM string. Standardize a single empty-state affordance (muted icon + one-line guidance + suggested command) and a single hint style, applied everywhere, so guidance always looks the same.
commands/info.py:117–119 · core/output.pyRun a subcommand wrong — boost snapshot with no action — and you get raw, unstyled argparse: a multi-line usage dump with a bare error:, nothing like the branded help. Route argparse's usage/error through the Aurora output layer (accent the program name, dim the usage grammar, use the standard Error: affordance) so failure looks as designed as success. Bonus: a "did you mean …" suggestion for unknown commands.
cli.py · argparse formatterOne source of truth for the brand — and the tools to show it off.
style/ vs docs/style/Two copies of boost.css have diverged: the root style/ uses a cyan→violet→pink gradient (--violet #a855f7), while docs/style/ uses an orange→pink→violet one (--violet #a78bfa). Same brand, two looks. Pick style/ as canonical and make docs/style/ a generated copy or symlink so the portfolio, roadmaps and CLI can't drift again.
style/boost.css · docs/style/boost.cssThe palette lives only in CSS; the CLI would hard-code its own copy of the same hexes — guaranteeing drift. Emit both from one tokens.json: generate the CSS custom properties and the Python ANSI map from it, so a brand change updates the site and the terminal in lockstep. Fits the repo's existing "generate, never hand-edit" pattern (cf. build_registries.py).
scripts/ · new build_tokens.pyThere's a docs/demo.tape + demo.gif, but no repeatable way to re-record once the aesthetic changes — and tmux isn't even installed in the dev box. Add a make demo that drives a scripted session (VHS tape or asciinema, optionally split-pane via tmux) and refreshes the GIF, so the README and portfolio always show the current look.
docs/demo.tape · MakefileThe web .window mock shows an idealized boost session — gradient prompt, clean checks — that the real CLI doesn't yet produce. Once D01–D15 land, update the mock (and README code blocks) to mirror the true output 1:1, so every screenshot is honest and the brand reads identically across web, README and terminal.
docs/index.html · README.md · style/demo.html
A living document — each loop iteration drives the real CLI, grades it against
style/boost.css, and files what it finds here. Sibling to the
Engineering Roadmap.
Everything stays zero-dependency and honors NO_COLOR & non-TTY.