If you look at my GitHub, it looks like a graveyard of "next big things." I have over 20 private repositories that follow the exact same lifecycle: I get a massive burst of inspiration. I spend 3 days over-engineering the perfect architecture. I hit the first boring/hard part (usually auth or marketing). I abandon the project and start a new one. For a long time, I thought the problem was my tech stack or my discipline. But after reading some clinical psychology papers on behavioral sabotage in high-performers, I realized it wasn't a code problem. It was an Ego Threat Response. So, being a developer, I did what developers do: instead of going to therapy, I built a local JavaScript profiling engine to diagnose my exact behavioral flaw, and then engineered an AI System Prompt to act as a clinical intervention. Here is how I built it, and how you can test it on yourself. The Architecture of Sabotage I needed a way to map specific developer behaviors to clinical psychological profiles.…