Optimized Neon Mode

Cyberpunk-inspired neon-glow statusline theme with vibrant color cycling, futuristic formatting, and high-contrast visual elements.

When to Use This Setting

Apply this setting when you need to:

• Transform your Claude Code statusline into a visually striking neon-themed display with color cycling effects
• Create a high-contrast, visually distinctive terminal aesthetic for dark-themed development environments
• Stand out with a cyberpunk-inspired coding environment during streams, recordings, or pair programming Consider alternatives when:
• You work in a light terminal theme where neon colors produce poor contrast and reduced readability
• Your terminal emulator does not support ANSI color codes or 256-color mode

Quick Start

Configuration

Copy
name: optimized-neon-mode
type: setting
category: statusline

Example Application

Copy
claude setting:apply optimized-neon-mode

Example Output

Setting applied. Changes:
- statusLine.type: command
- statusLine.command: bash neon-mode-display inline
- color_mode: ANSI 256-color with cycling
- glow_elements: brackets, separators, icons
- theme: cyberpunk-dark optimized

Core Concepts

Neon Mode Overview

Aspect	Details
Color Cycling	Rotates through neon pink, cyan, green, and purple on each refresh interval
Glow Brackets	Uses Unicode box-drawing characters and bright ANSI colors to create a glow effect
Icon Set	Replaces standard emoji with neon-themed Unicode symbols for consistency
Model Display	Wraps the Claude model name in neon-styled brackets with highlight colors
Directory Display	Shows current working directory with a neon folder icon and colored text

Neon Color Architecture

+-------------------+     +---------------------+     +------------------+
| Refresh Trigger   |---->| Color Cycle Engine  |---->| ANSI Code Mapper |
| statusline poll   |     | time % 4 = index    |     | pink/cyan/green  |
+-------------------+     +---------------------+     | purple palette   |
                                   |                   +------------------+
                                   v                          |
                          +---------------------+             v
                          | Glow Formatter      |    +------------------+
                          | box-draw + bright   |--->| Status Assembler |
                          | ANSI escape codes   |    | neon output line |
                          +---------------------+    +------------------+

Configuration

Parameter	Type	Default	Description
color_palette	string[]	["pink","cyan","green","purple"]	Neon colors to cycle through on each refresh
glow_intensity	string	"bright"	ANSI brightness level: normal, bright, or bold-bright
cycle_speed	string	"per-refresh"	How often the color advances: per-refresh, per-second, per-minute
bracket_style	string	"box-draw"	Style for enclosing elements: box-draw, angle, square, round
fallback_mode	boolean	true	Use plain text when terminal does not support 256-color ANSI

Best Practices

1. Verify terminal color support first - Run tput colors in your terminal to confirm 256-color support. If the output is less than 256, enable the fallback_mode parameter so the statusline degrades gracefully to basic ANSI colors instead of displaying broken escape codes.
2. Pair with a dark terminal theme - Neon colors are designed for dark backgrounds. If you use a light terminal theme like Solarized Light, the neon colors will wash out. Switch to a dark theme such as Dracula, Tokyo Night, or One Dark for optimal visual impact.
3. Reduce cycle speed for reduced motion preferences - If rapid color changes cause visual fatigue, set cycle_speed to per-minute so the color only shifts once per minute rather than every statusline refresh, maintaining the neon aesthetic without constant motion.
4. Customize the color palette for brand consistency - Replace the default neon colors with your team or company brand colors to create a personalized but still visually striking statusline that maintains professional identity.
5. Test in your recording software - Some screen recording tools handle ANSI color codes differently than live terminals. If you plan to record tutorials or streams, verify the neon colors render correctly in your recording output before going live.

Common Issues

1. Garbled text with escape code fragments visible - Your terminal does not support the ANSI escape sequences used for neon colors. Enable fallback_mode or switch to a terminal emulator with full ANSI support such as iTerm2, Alacritty, or Windows Terminal.
2. Colors appear washed out or invisible - You are using a light terminal background. Neon colors rely on dark backgrounds for contrast. Switch to a dark color scheme in your terminal preferences.
3. Statusline flickers during color cycling - The terminal is redrawing the entire line on each color change. Reduce the cycle_speed to per-minute or ensure your terminal supports efficient partial line redraws to minimize visual flicker.