Prompt Engineering

Part one was about why the song tab needed pictures at all. This part is about what I actually typed to get there — and why I didn’t know the answer myself before I typed it. You knew what you wanted. Why not just plan the build yourself first? Because I genuinely didn’t know how. I’m not a developer. I know what I want the result to feel like — my daughter looks at a picture, taps it, hears a song — but I have no instinct for how that should be structured underneath. So I stopped trying to design it and just described the situation to Claude instead, the way I’d describe it to another parent, not to an engineer. ...

Every time I type a prompt that actually matters — one that solved a real problem or unlocked something I didn’t know how to do — I prefix it with //. That double slash is a convention I made up. It tells my Claude Code hook: this one is worth keeping. The hook saves it to a file. Eventually I want those files to feed an app that writes blog drafts automatically. That is the plan for episode 20 of this series. ...