Series
Configure Your AI Coding Environment
A five-part guide to setting up your .claude folder, CLAUDE.md, hooks, permissions, and cross-tool configuration — the prerequisite for every other agentic workflow.
5 parts · first published
- 01
The Two Configuration Layers Every AI Developer Needs
Global rules that follow you everywhere. Project rules that stay with the code. Getting these two layers right is the single highest-leverage thing you can do before your first agentic session.
· 7 min read - 02
Writing CLAUDE.md That Agents Actually Follow
A 1,500-line CLAUDE.md doesn't make agents more consistent — it makes them less. The agents that work best have short rules backed by tooling, not long rules backed by hope.
· 8 min read - 03
Hooks That Pay for Themselves
A session-start hook runs once, costs nothing, and gives your agent context it would otherwise ask for or guess wrong. The highest-leverage 10 lines you'll write this week.
· 7 min read - 04
Project Settings, Permissions, and Team Sharing
What your team shares, what stays personal, and how to stop the 'Claude asked me to approve running npm install' prompts that break every flow.
· 6 min read - 05
Not on Claude? The Cross-Tool Configuration Guide
The concepts in this series aren't Claude-specific. Every major AI coding tool has a configuration layer. Here's how they map — and what Windows and Linux users need to know.
· 8 min read