Every time I work out how to do something well with these tools, I write it up: first for my team, then for friends at other companies, now here. Four guides. Two assume nothing at all, two assume you are a product manager who wants the full setup. All of them are free, and all of them are built to be forwarded.
No technical background, no terminal, no product job required. A pair of companion guides: the first explains what Claude is and how to work with it, the second turns that into workflows you can copy. Read them in order.
How the model actually works, what separates a good prompt from a bad one, when to start a new thread, and the difference between Chat and Code. Then Projects, Skills, Connectors, teaching it your voice, and picking a model. Every term is explained on the way past.
Read Claude 101The answer to “okay, but what do I do with it?” Automate a recurring chore, pull one report from many tools, produce a standardized deliverable every time, and hand off your to-do list. Ends with five steps for building your own.
Read the PlaybookThese assume you want Claude in your actual job: reading the repo, drafting the ticket, running the analysis while you sleep. Some setup is involved, and the guides walk you through all of it.
A complete setup-and-workflow guide for non-engineering PMs. Five parts: overview, one-time setup, daily use, tips, and a five-week onboarding path. Built to hand to a new hire.
Read the guideI wrote this when I migrated from ChatGPT to Claude. It asks your old AI to summarize what it knows about you and produces three files: a context doc, a custom-instructions block, and a memory dump.
Read the promptTell me what worked and what didn’t. Every one of these got better because someone sent me a question I hadn’t thought to answer.