Guides
Plain-English guides for people who work with Claude Cowork and Claude Code and aren’t programmers.
Why Does Claude Ignore CLAUDE.md? (And What Actually Makes Rules Stick)
Why does Claude ignore CLAUDE.md? It reads the file as context, not as orders. Here is why rules get skipped and what makes them stick, in plain English.
Read the guide →AI says “task completed” but didn’t? How to check in five minutes
AI says “task completed” but didn’t do the work? A 5-minute check for non-programmers: open the file, check its date, compare counts, ask for proof.
Read the guide →Can Claude Cowork Delete Files? What Stops It, and What Doesn't
Can Claude Cowork delete files? Only in folders you connect, and it must ask first. Why that prompt isn't enough, and how a trash folder and backups help.
Read the guide →Claude Cowork Instructions vs. CLAUDE.md: What Goes Where
Claude Cowork instructions vs. CLAUDE.md: what the official docs say each one loads, what our tests showed, and a simple table of where each rule belongs.
Read the guide →How to Make Claude Remember Previous Chats (and the Decisions You Made in Them)
How to make Claude remember previous chats: what memory and chat search do, where they stop, and why your decisions belong in files that load each time.
Read the guide →How to Write Claude Cowork Global Instructions That Actually Hold (No Template Needed)
How to write Claude Cowork global instructions without a template: what belongs there, what to leave out, why short holds better and why rules need proof.
Read the guide →