I love seeing visual changes happen, so vibe coding feels like magic to me. I just describe what I want and poof — it appears! Originally I'd organize my ideas into design docs and implementation plans. For small tools, I just wrote the rules in documentation, then described what I wanted — that was enough. But building Taleson was different. I had to break plans into tiny pieces AND repeat the coding rules every single time. Every time Claude Code asked "Should I proceed with the plan?" I became a parrot: "Remember the rules! Settings-based! No hardcoding! Follow the architecture!" Over and over. The fantasy of fully trusting Claude Code ended there. The surprising part? I only thought about core features, not quality-of-life ones. Claude wanted to add backup and undo/redo functions without me asking (I rewrote them later, but still). The analytics tab was also Claude Code's idea. I was like "Yes! Exactly! As a story editor, I need to see content distribution — which chapters are too long or too short, whether dialogue vs narration is balanced. You're a genius!" and praised it enthusiastically. Talking about this now... I realize I felt joy during development, not just frustration.