Give the banner some flavor: welcome line, sparkle accents, command guide - #9
Merged
Merged
Conversation
…uide Took inspiration from Claude Code's splash screen (not its specific mascot/scene) and built something in mpesa-dev's own voice instead of a blank two-line tagline: - A "Welcome to mpesa-dev." line up front, so the first thing on screen isn't silence - Ambient sparkle accents (✦ ·) flanking the M mark in gold/yellow — a loose-change motif fitting a money-movement tool, not a literal copy of any specific scene - A quick command guide underneath (doctor/inspect/tunnel/replay, one line each) so the one time this banner is seen, it also teaches what's here — inspect is marked "← starting now" since that's exactly what happens next - Kept the M mark's existing gradient untouched (it already worked well) Verified rendering both with and without COLORTERM=truecolor (sparkles use colored's basic yellow(), so they're identical either way — no fallback risk), and confirmed the production-environment yellow highlight still fires correctly alongside the new content.
There was a problem hiding this comment.
Pull request overview
This PR enhances the mpesa-dev startup banner to be more informative and visually engaging when the CLI is run with no subcommand, while preserving the existing “M” gradient styling.
Changes:
- Adds a bold “Welcome to mpesa-dev.” line above the mark.
- Adds yellow sparkle accents above/below the mark.
- Adds a brief, colorized command guide (doctor/inspect/tunnel/replay) beneath the environment line.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Command guide's "starting now" note used a bespoke "←", inconsistent with the icon module's documented arrow (→, "an action or pointer to something the user should do next" — which is exactly what this is). Switched to icon::arrow(). - print_command_guide() hard-coded subcommand names/descriptions, duplicating the Command enum's doc comments in cli.rs and liable to drift if a subcommand changes. banner::print_full() now takes the guide's (name, about) list as a parameter instead of hard-coding it; main.rs builds it from Cli::command().get_subcommands(), the same clap metadata --help already uses, filtering out the auto-generated "help" pseudo-subcommand. Verified: the printed guide's descriptions now match --help exactly (e.g. "Run sandbox connectivity and config checks" instead of a paraphrased "diagnose your Daraja setup"), confirmed --help itself is unaffected, and build/clippy -D warnings/fmt --check/test all pass.
DENNIS-CODES
added a commit
that referenced
this pull request
Aug 11, 2026
- Command guide's "starting now" note used a bespoke "←", inconsistent with the icon module's documented arrow (→, "an action or pointer to something the user should do next" — which is exactly what this is). Switched to icon::arrow(). - print_command_guide() hard-coded subcommand names/descriptions, duplicating the Command enum's doc comments in cli.rs and liable to drift if a subcommand changes. banner::print_full() now takes the guide's (name, about) list as a parameter instead of hard-coding it; main.rs builds it from Cli::command().get_subcommands(), the same clap metadata --help already uses, filtering out the auto-generated "help" pseudo-subcommand. Verified: the printed guide's descriptions now match --help exactly (e.g. "Run sandbox connectivity and config checks" instead of a paraphrased "diagnose your Daraja setup"), confirmed --help itself is unaffected, and build/clippy -D warnings/fmt --check/test all pass.
DENNIS-CODES
added a commit
that referenced
this pull request
Aug 11, 2026
…enz0d Give the banner some flavor: welcome line, sparkle accents, command guide
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up on feedback that the bare
mpesa-devbanner felt too blank/quiet. Took inspiration from Claude Code's splash screen — not its specific mascot/scene, since that's Anthropic's own product identity — and built something in mpesa-dev's own voice instead.doctor/inspect/tunnel/replay, one line each), so the one moment this banner is seen, it also teaches what's here —inspectis marked← starting nowsince that's exactly what happens nextTest plan
cargo build --all-targets,cargo clippy --all-targets -- -D warnings,cargo fmt --all -- --check,cargo testall passCOLORTERM=truecolor— the sparkles usecolored's basicyellow(), so they're identical either way, no fallback riskproduction-environment yellow highlight on theEnvironment:line still fires correctly alongside the new contenthttps://claude.ai/code/session_01BE4uE4wMaDgqN43zXvbqHH
Generated by Claude Code