The /hatch command connects your Claude workspace to your real tools and data. Learn what it does, why it matters, and how it works.
You download a workspace from The Froject. It has skills, commands, agents, rules, and a well-structured CLAUDE.md. But it's still generic. The brand voice section says "describe your brand voice here." The context files have placeholder text.
/hatch is the command that brings your workspace to life. When you run it, Claude walks you through three things.
Before: you type "write a blog post" and Claude asks what your brand voice is.
/hatch is a command file in your workspace that triggers a guided setup process. It reads your workspace configuration, identifies what needs to be connected or filled in, and walks you through each step.
No. Your workspace works without it. But it works much better with it. /hatch is what turns a generic workspace into your workspace.
Yes. If you add new tools or want to update your context, run /hatch again. It picks up where you left off.
No. Everything stays on your machine. Tool connections run locally through MCP. Your data never leaves your computer.