Why I Vibe Code Like an Artist (14 Months of Unity Dev)

👉 Wishlist on Steam: https://store.steampowered.com/app/40... I'm building my game solo using Claude Code, and this month is all about how I prompt. What most people would call a "bad prompt" is often my best one. In this video I explain why I intentionally give the least amount of information possible, why telling the model "this looks terrible" is genuinely useful feedback, and how my background as a 3D modeler and animator led me to a start-broad-then-narrow approach that comes straight from art training, not programming. I also show why I stopped using MD files as prompts in favor of a local wiki page system, and then I vibe code a real feature: enhancing the visual juice of my water potion, picking between three variations Claude built for me, and iterating on the winner until it feels right. Finally, I share my playtest results honestly. I made every mistake an amateur game designer makes, and game design is the one bottleneck Claude can't help me with. Timestamps: 00:00 – Intro 01:48 – My "Bad" Prompts 02:54 – Prompt Like an Artist 03:58 – Management Styles 04:42 – Broad to Narrow 06:15 – Main Downside 07:15 – Ditching MD Files 08:06 – Animation Polish 10:28 – Me Actually Vibe Coding 13:00 – Picking a Winner 15:16 – My Feedback Loop 17:53 – Playtest Results