Lily
Posted on Jul 14
• Originally published at dev.to
This is a follow-up to my previous post on getting Claude Code to improve itself unattended. This time the topic is a different problem: a mechanism to stay aware of your environment as it balloons.
Skills piled up under ~/.claude/, launchd jobs multiplied, and once my project count crossed into the double digits, I could no longer answer off the top of my head "how many layers is the whole thing, and what's running right now?" Rather than typing ls every morning, I wanted a state where opening Obsidian gives me the bird's-eye view. So I wrote ~/.claude/scripts/env-map.sh.
