Custom Neon Standard

Balanced neon-themed statusline combining soft glow aesthetics with practical development information in a clean layout.

When to Use This Setting

Apply this setting when you need to:

• Apply a neon visual theme that is less intense than full neon mode while still providing visual flair
• Maintain readable, practical statusline information wrapped in a subtle neon-styled presentation
• Create a consistent neon look that works well across both dark and medium terminal themes Consider alternatives when:
• You prefer the full cyberpunk intensity of the optimized neon mode setting
• You want a purely functional statusline with no decorative theming at all

Quick Start

Configuration

Copy
name: custom-neon-standard
type: setting
category: statusline

Example Application

Copy
claude setting:apply custom-neon-standard

Example Output

Setting applied. Changes:
- statusLine.type: command
- statusLine.command: bash neon-standard inline
- theme_intensity: soft-glow
- info_fields: model, directory, git-branch, time
- color_mode: ANSI basic with selective highlights

Core Concepts

Neon Standard Overview

Aspect	Details
Theme Intensity	Soft-glow approach using muted neon tones rather than full-bright cycling
Color Application	Selective highlighting on key fields (model, branch) while keeping text in neutral tones
Information Fields	Shows model name, working directory, git branch, and timestamp in a structured layout
Compatibility	Uses basic ANSI colors (8/16) ensuring broad terminal compatibility
Layout	Pipe-separated fields with subtle neon-colored brackets around primary identifiers

Neon Standard Architecture

+-------------------+     +---------------------+     +------------------+
| Session Input     |---->| Field Extractor     |---->| Theme Applicator |
| JSON via stdin    |     | model, dir, branch  |     | soft-glow rules  |
+-------------------+     +---------------------+     +------------------+
                                   |                          |
                                   v                          v
                          +---------------------+    +------------------+
                          | Git Branch Reader   |    | Neon Formatter   |
                          | symbolic-ref HEAD   |--->| highlight + mute |
                          +---------------------+    | structured line  |
                                                     +------------------+

Configuration

Parameter	Type	Default	Description
highlight_color	string	"cyan"	ANSI color applied to primary fields like model name and branch
muted_color	string	"white"	ANSI color for secondary text like separators and directory name
show_git_branch	boolean	true	Include the current git branch in the statusline display
show_timestamp	boolean	true	Show current time in HH:MM format as the last statusline field
bracket_color	string	"magenta"	ANSI color for the subtle brackets around highlighted fields

Best Practices

1. Choose highlight colors that complement your terminal theme - The default cyan works well on most dark themes, but may be hard to read on certain color schemes. Test with your actual terminal theme and adjust highlight_color to a tone that provides good contrast without being harsh.
2. Use neon standard as a stepping stone - If full neon mode is too intense and minimal standard is too plain, neon standard provides the middle ground. Start here and gradually increase or decrease the theming based on your daily comfort level.
3. Coordinate with team color conventions - If your team uses color-coded branch naming or environment indicators, align the neon standard highlight colors to avoid confusing similar-colored elements that represent different things.
4. Disable git branch in non-repo directories - When working outside git repositories, the branch field shows an error. Set show_git_branch to false if you frequently work in non-git directories to keep the statusline clean.
5. Test with screen readers - If you or team members use accessibility tools, verify the ANSI color codes do not interfere with screen reader output. The neon standard's basic ANSI approach is generally more compatible than 256-color alternatives.

Common Issues

1. Colors show as plain white text - Your terminal is in monochrome mode or does not support ANSI color codes. Check your terminal emulator settings and enable color support, or verify the TERM environment variable is set to a color-capable value like xterm-256color.
2. Git branch displays an error message - The current directory is not a git repository. This is expected behavior. Either navigate to a git repository or disable the show_git_branch parameter to suppress the error.
3. Brackets appear as raw characters instead of colored - The ANSI escape sequences are not being interpreted. Ensure your statusline command runs through bash and not a shell that strips escape codes. Verify with echo -e "\033[36mtest\033[0m" in your terminal.