What to bring to Claude

On your tool map, Claude is the careful workhorse: the desk for heavy inputs and outputs that have to hold together. This opening lesson is about fit — which of your actual tasks belong here, which don't, and why the difference matters more at this desk than anywhere else. (Product specifics in this course are current as of September 2026.)

Bring the long and the layered. Claude's signature strength is sustained work over big material: a forty-page contract, a season of correspondence, a report that has to stay coherent from page one to page nine. Where a quick tool sprints, this one keeps its grip — the tenth page of output remembers what the first page promised, and the answer about section 12 actually reflects sections 1 through 11.

Bring the work that repeats around one subject. Ongoing threads — a client, a product line, a filing season — benefit from Claude's project workspaces, where instructions and reference files persist. If a task belongs to a body of work rather than to a moment, this desk is set up for exactly that shape; the setup lesson next makes it concrete.

Bring the drafts where being wrong is expensive. Careful is a temperament as much as a capability: Claude tends toward acknowledging uncertainty and following long instructions closely. That makes it a strong fit for text with consequences — the policy note, the scope-of-work, the difficult letter — where you want the constraints honored on the first pass, not negotiated across six.

What not to bring. Live facts and current events — that's the researcher desk's job (though Claude can search when asked, treat sourced research as the specialist's game). Quick throwaway drafts where setup outweighs the task. And anything a human professional must own — the same boundary as everywhere: drafts here, decisions with the person whose name goes on them.

Everything transfers. Your five-part asks, tone layers, templates, fix-loops, the thirty-second check — all of it works here unchanged. This course adds what's specific: projects and their memory, document workflows at scale, structured-data care, and the deeper reasoning modes. You're not learning a new language, just a new desk's strengths.

A note on how it reads you. Long, structured asks get rewarded here: numbered constraints honored as a checklist, multi-part questions answered part by part, formats followed to the letter. That has a practical consequence — the effort you put into a careful ask isn't politeness, it's leverage, and sloppy asks waste this desk specifically. If the five-part structure ever felt like ceremony at the quick desk, here is where it visibly earns its keep: the more precisely you specify, the more precisely you receive.

One mistake to skip: loyalty. The point of this course is not that this desk is best — it's that it's best for a shape of work. People who route everything to one tool pay in mismatch: quick tasks get ceremony, heavy tasks get shortcuts. Keep the map from Foundations on the wall; this course just details one region of it.