The reason I want everyone to learn to vibe code, ai engineer, and prompt prompt prompt is not because I think building good products is trivial. It’s because I think creating something exceptional is still really hard. Too much out there treats the making of the thing = the most important thing and my pov is that that making of the thing is so unimportant to its actual success we *should* commodify it. So we can spend our time & creativity where it counts: figuring out the right problem, getting in the market, wrestling with user needs and figuring out how to commercialize them. Making things *can* be high leverage when you have a thing: PMF benefits from rapid cycles and ambitious plans. Speed wins. Impossible ideas become impossible. All these things are good and accelerated by AI. But beware of anyone who helps you develop a skill but can’t tell you how to usefully apply it. You’ll feel productive, but not produce. Know where making fits. And what it can’t solve.

Paging @yashdulla

I read dozens of posts about @claudeai skills and not one mentioned you have to make a .zip file Which is why I’m starting How I AI mini episodes, where I give my quick, hands-on take on new AI releases and how best to get started with them. In our first mini ep, I walk through - what skills are - (trying to) use Claude to make them - more successfully using @cursor_ai to make them - accessing and running them in both Claude code and the chat interface Less than 30 minutes, practical, and a no-judgement zone for beginners. Mini-eps are sponsored by @chatprd Check the first one out on YouTube: