Claude, for the rest of us
One page that makes you better at Claude, and a short note each week when something changes.
I am Jake Knight. I coach executives on using Claude without becoming engineers. This is the page I hand every client, kept current, with a plain-English note when Claude changes and it matters to you.
Three of the six entries, free
Set up: a project is a folder
Checked Oct 2026One project per recurring job. Its instructions load into every chat, so you stop re-explaining yourself.
One chat per topic. Start a new one when the answers get weird, or when something is in the chat that you do not want leaking into the next answer.
Copy files into the folder. Never move the originals.
Ask: three pieces of a good prompt
Checked Oct 2026- Context
- What it needs to know. Where things live, what you already have.
- Task
- The one thing to do. Not three.
- Rules
- Format, length, what not to do, where the result goes.
Talk it, do not type it. More context in, better answer out.
Plan, don't polish
Checked Oct 2026Ask for the plan. Fix the plan. Then build. Claude is good at planning and bad at revising something it already finished.
Small change: make it yourself. Big change: change the plan and run it again.
If it asks you a question after the plan, you missed it in the plan.
The other three, the print layout, and every update are for members.
What you get
- The one-page cheat sheet, as a web page and as a PDF. Print it and keep it by the keyboard.
- A short weekly note on what changed in Claude and what it means if you are not a programmer.
- Every entry carries the date I last checked it, so you know it is still true.
Join
Already a member? Sign in by email.