Decide What Claude Can Do on Its Own, Complete Resource Pack
An exclusive resource for students of Arun's Claude Code Course.
The thing you actually keep out of this section is a file sitting in your project with a line in it that you typed. Everything else on this page exists to get you there.
The page you build your own file from
Your Claude Code Permissions File, and What Every Line Does
Your starting point, plus every line explained underneath it. Copy it into a folder called .claude at the top of your project, save it as settings.json, and then add your own commit line at the bottom of the allow list. That one line is the decision in there that belongs to you rather than to me.
The last part of that page is the diagnosis for the day a rule you wrote correctly goes quiet on you. Three things decide whether your rule applies and none of them is the text of the rule.
For switching posture mid-job
Desktop App Shortcut Sheet
The mode menu, the effort menu and the model list are each one shortcut away. Keep it open for the first week, while thinking in plan, acting in accept-edits and verifying in the careful default is still something you have to think about.
To check a detail yourself
The Official Permissions and Settings Documentation
This area moves, and a page updates faster than a lecture does. It is also where you can read what bypass permissions actually turns off, which is worth doing before you go anywhere near it.
To try the handover once
Plan Mode Trial Run
A small, real request you can run in plan mode to watch what happens when a plan finishes, because Claude does not simply start building.
The line worth keeping
Everything on one side of it is Claude writing. Everything on the other side is Claude running.
Which side a job sits on is something you can work out before you start it, and it has nothing to do with how much you trust Claude. A file Claude wrote is sitting there and you can read it, and your saved history puts it back on one command. A command Claude ran does not appear in that comparison anywhere. It happened, and the only trace of it is whatever it did to your machine.
See Where You Stand
This resource is one piece of a much bigger system.
Take the free Claude Code Readiness Quiz. It is 15 short situations, scored out of 100, and it tests how you handle a job rather than what you know about a tool, so you can take it without ever having opened Claude Code.
Take the Claude Code Readiness Quiz →15 situations · Scored out of 100 · Free