Transcription
Most people don't realize that the cloud folder is the single most important part of your claude code workflow. Here are the only four files that matter and how to set them up.
First is your cla.md. This is your most important file. Claude reads it before every session. You put your build commands, your architecture decisions, your naming conventions, and your gotchas in here. Keep it under 20 lines; any longer and claude actually starts ignoring parts of it.
The rules folder. Instead of one giant instruction file, you split rules by concern. Code style in one file, testing standards in another file, and API conventions in another file. And you can scope them by file path. So Cloud only loads API rules when it's working in your API folder.
Settings.json. This is your permission system and safety rules. You define what Claude can run without asking, what is entirely blocked, and what it needs to ask you about first before doing anything. You should allow your build scripts and deny anything that touches your EM file or have destructive commands. This is the one that most people miss out on.
Hooks file. These are scripts that fire automatically at specific points. A hook that runs your formatter every single time Claude finishes editing a file. A hook that blocks dangerous batch commands before they execute. Even hooks that run your test suite will not let Claude say done until everything finishes.
I created a detailed guide in building out these four files. Just comment "file" and I'll send it to you.