Made
Crystal ClearBrowse series

Claude Code Made Crystal Clear · chapter 1: What Claude Code Is, and Why Developers Won't Shut Up About It

Every surface is a different doorway into the same engine

2026-08-27

The sentence that matters most in that list is this one from the overview: "Each surface connects to the same underlying Claude Code engine, so your CLAUDE.md files, settings, and MCP servers work across all of them." CLAUDE.md is a project file the agent reads at the start of every session (chapter 5 is devoted to it), and MCP servers are connections to external tools (chapter 9). The point for now: you configure the agent once, and that investment follows you from terminal to IDE to phone. Figure 1.2 shows the hub-and-spoke picture.

Figure 1.2: Every surface is a different doorway into the same engine. Configuration you write once (CLAUDE.md, settings, MCP servers) applies everywhere.
Figure 1.2: Every surface is a different doorway into the same engine. Configuration you write once (CLAUDE.md, settings, MCP servers) applies everywhere.

This diagram is one of many in Claude Code Made Crystal Clear.

Every chapter opens with the gist, draws the hard ideas, and ends with recipes and sources.

Get the book

More from this book

The chat workflow routes every step through you

All diagrams