Configured Data Ocean Statusline

Dive into an ocean-themed statusline that visualizes codebase depth, sea creatures, and rare treasure discoveries.

When to Use This Setting

Apply this setting when you need to:

• Transform your Claude Code statusline into an immersive ocean-depth metaphor that maps file count to exploration depth
• Add gamification elements like rare treasure drops and creature encounters to long coding sessions
• Visually distinguish project complexity at a glance through depth-based sea creature indicators Consider alternatives when:
• You prefer a minimal, information-dense statusline without decorative elements
• Your terminal does not render Unicode emoji characters correctly

Quick Start

Configuration

Copy
name: configured-data-ocean-statusline
type: setting
category: statusline

Example Application

Copy
claude setting:apply configured-data-ocean-statusline

Example Output

Setting applied. Changes:
- statusLine.type: command
- statusLine.command: bash ocean-depth scanner
- depth_multiplier: 10m per source file
- creatures: whale(>100m), fish(50-100m), small-fish(<50m)
- treasure_chance: 5% per interaction

Core Concepts

Ocean Depth Mapping Overview

Aspect	Details
Depth Calculation	File count multiplied by 10 (meters) for .py, .js, .rs files
Wave Patterns	Randomly cycles through ocean, whirlpool, droplet, electric, fire
Creature Tiers	Whale appears above 100m depth, fish at 50-100m, small fish below 50m
Treasure System	5% chance per interaction to discover a diamond treasure icon
File Scanning	Uses find to count Python, JavaScript, and Rust source files

Ocean Statusline Architecture

+---------------------+     +------------------+     +----------------+
| File System Scanner |---->| Depth Calculator |---->| Creature Logic |
| find *.py *.js *.rs |     | files * 10 = m   |     | depth thresholds|
+---------------------+     +------------------+     +----------------+
         |                          |                        |
         v                          v                        v
  +-------------+          +-----------------+       +---------------+
  | Wave Picker |          | Treasure Roller |       | Status Output |
  | RANDOM % 5  |          | RANDOM % 20     |       | concat fields |
  +-------------+          +-----------------+       +---------------+

Configuration

Parameter	Type	Default	Description
depth_multiplier	integer	10	Meters per source file found in the project tree
file_extensions	string[]	[".py",".js",".rs"]	File types counted for depth calculation
treasure_probability	float	0.05	Chance of treasure appearing each refresh cycle
wave_set	string[]	["ocean","whirlpool","droplet","electric","fire"]	Pool of wave pattern icons to cycle through
creature_thresholds	object	{whale:100,fish:50}	Depth boundaries for creature tier assignment

Best Practices

1. Calibrate depth multiplier for your project - Large monorepos with thousands of files can push depth into unrealistic ranges. Lower the multiplier to 5 or even 1 if your project exceeds 500 source files so the creature tiers remain meaningful and visually varied.
2. Extend file extensions for your stack - The default configuration only scans Python, JavaScript, and Rust files. Add your primary language extensions such as .ts, .go, or .java to the file_extensions array so the depth reading accurately reflects your full codebase.
3. Use alongside git-aware statuslines sparingly - Running multiple statusline commands simultaneously can create terminal flicker. If you want both ocean depth and git branch information, consider forking the script to embed git data within the ocean display rather than running two separate statusline commands.
4. Monitor find command performance - The file scanning step executes find on every refresh. For projects with deeply nested node_modules or vendor directories, add exclusion patterns to prevent slow scans that delay your statusline rendering.
5. Customize treasure for team milestones - Replace the default treasure icon and probability to celebrate team events. For example, set treasure to 100% probability during release days to give every developer a visual reward during deployment windows.

Common Issues

1. Depth always shows 0m - The scanner only counts .py, .js, and .rs files by default. If your project uses different languages like TypeScript or Go, update the file_extensions configuration to include your actual source file types.
2. Wave icons display as question marks - Your terminal font lacks emoji support. Install a Nerd Font or emoji-capable font such as JetBrains Mono NF and configure your terminal emulator to use it as the primary or fallback font.
3. Statusline refreshes slowly in large repositories - The find command traverses the entire directory tree including node_modules and .git folders. Add -not -path '*/node_modules/*' and similar exclusions to the find command within the statusline script to reduce scan time.