The Leaky Funnel@theleakyfunnelTake me to the agency siteClaude Code tips, part 1
Three habits from the official Claude Code docs that save the most time: a memory file, plan mode, and a clean slate between jobs. They work in any folder, not just code.
Skip the reading: hand it to Claude
Copy the whole guide and paste it into Claude, or install it as a Claude Code skill so it’s always there.
Save it as ~/.claude/skills/claude-code-tips-part-1/SKILL.md, then ask Claude Code to “claude code tips, part 1”.
The prompts
Write my CLAUDE.md rules
Paste after running /init.
Add a "House rules" section to CLAUDE.md for my business. Ask me 6 short questions first: what we sell, who the customers are, tone of voice, spelling (UK or US), things you must never do (for example: send emails, delete files, change prices), and where the important files are. Then write the rules as short bullet points.
Plan first
Use in plan mode for any bigger job.
[DESCRIBE THE JOB]. Before changing anything, read what you need in this folder and give me a step-by-step plan: what you'll change, which files, and what could go wrong. Wait for my yes.
Setup
Tip 1: in your folder, run /init. Claude writes a CLAUDE.md file. Each session starts with a fresh memory, so add your standing rules to this file once.
/initTip 2: press Shift+Tab until the status line shows plan mode. Claude reads and proposes a plan, but makes no changes until you approve it.
Tip 3: run /clear between unrelated jobs. The next task then doesn't carry the last one's history.
/clear
What I use
- Claude CodeWorks in any folder: code, documents, notes.
- Memory (CLAUDE.md)Official docs for tip 1.
- Common workflowsOfficial docs for plan mode.
- Best practicesOfficial docs for /clear.
Worth knowing
- If Claude goes off track twice on the same job, run /clear and start again with a clearer brief. The docs recommend it, and it's usually faster than correcting.