Claude Code Tips
How I use Claude Code across client work: configuration, memory, custom agents, permissions and automation, plus the mistakes that taught me each rule.
- Tips
- 9
- Updated
- Aug 2026
// foundations
01–02- 01
Your CLAUDE.md Is a Contract, Not Documentation
Most CLAUDE.md files fail because they describe a project instead of constraining behaviour. Here is the one I actually use, rule by rule, and why each line earns its place.
claude codeai toolingdeveloper workflowproductivity - 02
Giving Claude a Memory That Outlives the Session
Context windows end. Projects do not. Why I keep my AI's long-term memory in an Obsidian vault instead of a config file, and the rules that decide what gets written.
claude codeobsidianai toolingdeveloper workflow
// extending
03–06- 03
Skills, Agents, Commands, Plugins: Which One Do You Actually Need?
Four ways to extend Claude Code, overlapping enough to be confusing. A decision rule for each, based on what happens to your context window.
claude codeai toolingdeveloper workflowautomation - 04
Building Domain Agents That Know Your Stack
A subagent is a job description, not a personality. What goes in one, why my code reviewer cannot write files, and why most of them run on a cheaper model.
claude codeai toolingcode reviewdeveloper workflow - 05
Why I Turned Off Auto-Compact
Automatic context compaction saves a session from dying. It also silently rewrites what your assistant believes. Here is the trade, and what I do instead.
claude codeai toolingcontext managementdeveloper workflow - 06
MCP Servers That Earn Their Place
Every MCP server you connect spends context before you type anything. Four that justify it, several that did not, and the test I use to decide.
claude codemcpai toolingdeveloper workflow
// in practice
07–09- 07
Debugging With an AI That Sounds Certain
A production site broke. The diagnosis was specific, evidence-backed, and wrong. What that session taught me about verifying confident answers.
claude codedebuggingcloudflaredeveloper workflow - 08
Permissions: What to Automate, and What Never To
Permission prompts are friction, and friction gets disabled. A framework for deciding what runs unattended, based on reversibility rather than danger.
claude codesecurityai toolingdeveloper workflow - 09
Loops, Background Jobs and Scheduled Agents
The last step is work that happens while you are not watching. Where that pays off, where it quietly burns money, and the rule that decides which.
claude codeautomationai toolingdeveloper workflow
Need a developer who ships fastwithout shipping mess?
I build and maintain WordPress, Laravel and Nuxt applications for businesses that care about performance and maintainability.