Custom Programming Fitness Tracker

Coding fitness statusline tracking steps, calories, intensity levels, and achievement badges earned through programming interactions.

When to Use This Setting

Apply this setting when you need to:

• Gamify your coding sessions with a fitness-themed tracker that counts interactions as steps and calories
• Earn visual achievement badges at milestone thresholds to reward consistent coding activity
• Monitor your coding intensity level as it cycles through walking, running, and sprinting phases Consider alternatives when:
• Fitness metaphors feel mismatched with your development workflow or team culture
• You prefer data-driven metrics like actual lines changed or commits made over gamified approximations

Quick Start

Configuration

Copy
name: custom-programming-fitness-tracker
type: setting
category: statusline

Example Application

Copy
claude setting:apply custom-programming-fitness-tracker

Example Output

Setting applied. Changes:
- statusLine.type: command
- statusLine.command: bash fitness-tracker inline
- steps_per_interaction: 1
- calories_per_interaction: 2
- badge_thresholds: bronze(50), gold(100)
- intensity_cycle: walking(0-29%), running(30-69%), sprinting(70%+)

Core Concepts

Fitness Tracker Overview

Aspect	Details
Steps Counter	Increments by 1 with each statusline refresh, persisted in session cache
Calorie Counter	Increments by 2 per interaction, representing coding energy expenditure
Activity Intensity	Cycles through walking, running, sprinting based on step count modulo 10
Achievement Badges	Bronze badge awarded at 50 steps, gold badge at 100 steps
Session Persistence	State stored in /tmp keyed by session ID for continuity across refreshes

Fitness Tracker Architecture

+-------------------+     +---------------------+     +------------------+
| Session Cache     |---->| Step Incrementer    |---->| Calorie Calc     |
| /tmp/fitness_*    |     | steps + 1           |     | calories + 2     |
| steps, calories   |     | per refresh cycle   |     | per refresh      |
+-------------------+     +---------------------+     +------------------+
                                   |                          |
                                   v                          v
                          +---------------------+    +------------------+
                          | Badge Evaluator     |    | Intensity Mapper |
                          | 50=bronze 100=gold  |--->| steps%10 ranges  |
                          +---------------------+    | walk/run/sprint  |
                                                     +------------------+

Configuration

Parameter	Type	Default	Description
steps_per_tick	integer	1	Number of steps added per statusline refresh interaction
calories_per_tick	integer	2	Number of calories added per statusline refresh interaction
bronze_threshold	integer	50	Step count required to earn the bronze achievement badge
gold_threshold	integer	100	Step count required to earn the gold achievement badge
intensity_cycle_base	integer	10	Modulo base for the walking/running/sprinting cycle calculation

Best Practices

1. Add more badge tiers for longer sessions - The default stops at gold at 100 steps. Add platinum at 250 and diamond at 500 to keep the badge progression meaningful during full-day coding sessions where you easily exceed 100 interactions.
2. Calibrate calorie values for humor - The calorie counter is purely for fun. Set it to exaggerated values like 50 calories per interaction for comedic effect, or lower it to 0.5 for a more realistic mental calories metaphor.
3. Use intensity cycling as a pace indicator - When you see the sprinting icon frequently, it means you are in a high-interaction phase. Use walking phases as natural moments to review your work and plan next steps.
4. Reset tracker for fresh motivation - Delete the session cache file when starting a new day or sprint. This gives you a clean slate and makes badge achievements feel earned within each focused work period.
5. Share milestones with your team - Post screenshots when you earn badges to create friendly competition. Some teams set collective step goals for the week, turning individual fitness tracking into a collaborative team challenge.

Common Issues

1. Steps count jumps unexpectedly - The cache file may be shared between multiple Claude Code sessions if session IDs collide. Ensure each session generates a unique ID prefix for the cache filename.
2. Badge never appears - The badge evaluation checks thresholds with the greater-than-or-equal operator. If your step count somehow skips the exact threshold value, verify the comparison logic uses >= rather than strict equality.
3. Intensity never changes from walking - The modulo cycle base may be set too high relative to your step count. Verify that steps_per_tick is incrementing correctly and that the modulo arithmetic produces values across all three intensity ranges.