Playbook8 chapters ·Updated Aug 2026

The Claude Playbook

Eight chapters on getting real work out of Claude, in the order that actually makes sense to learn them.

Most guides to AI tools teach you features. This one teaches a sequence, because the order matters more than the feature list.

Almost everyone starts in the same place: open a chat, type a request, get something bland back, conclude the tool is overrated. The problem is rarely the model. It is that a blank chat knows nothing about you, your clients, your standards or how you write, and you are asking it to produce senior work with none of that.

So the sequence below starts with making the tool yours, then teaches the one prompting idea worth learning, then makes that context permanent, then reframes how you build anything substantial. Only after that does it get into connectors, skills, scheduled runs and browser work. Those last four are genuinely powerful and almost useless if you skip the first four.

Each chapter ends with one thing to try on real work. Not an exercise. Something you were going to do anyway, done differently.

The examples are drawn from media and marketing, because that is the work I do. The method transfers to any knowledge work where the output is a document, a plan or a decision.

Foundation Make the tool yours, then change how you build. Skip these and the rest will not land.

01Set it up so it is actually yoursOut of the box it knows nothing about you, and the default settings will quietly cost you your usage limit. Five moves, about ten minutes.5 min read 02Anatomy of a good promptCollections of prompts to copy go stale in a month. One framework, learned once, improves every prompt you write after it.5 min read 03Make the context permanentThe last chapter said context does most of the work. This one stops you typing it out every single morning.4 min read 04Build it in stages, not one shotThis is the chapter that matters most. Everything before it was setup. This is the change in how you actually work.6 min read

Leverage Only worth switching on once the four above are habit. This is where the time comes back.

05Connect it to your filesYou have spent four chapters teaching it to work with what you hand it. This one stops you doing the handing.4 min read 06Turn a repeated task into one commandA project holds the context for a client. A skill holds the steps for a task. Once you see the difference, you stop retyping instructions forever.4 min read 07Let it run on a scheduleChapter six removed the typing. This one removes the starting. The work is already done when you sit down.4 min read 08Work where the tools have no integrationChapter five connected the systems that offer a connection. This one is about everything else, which in this industry is most of it.4 min read

Written by Bachir Zeidan in Dubai

← All writing