This is exactly

This is exactly how you should set up Claude code on your computer. Start with the global setup. There are three parts: your global CLAUDE.md file, your global skills, and your global agents. The global CLAUDE.md controls how Claude behaves across all your projects. Put your default coding style, your architecture preferences, your rules, your workflow habits there. But don't put project-specific instructions there. Then come global skills and agents. These are available everywhere, but they also take up context, so only make something global if you actually use it all the time. A planning skill, good. A workflow agent you use in every repo, fine. But anything specific to one app should stay inside that project. Now, project-level setup inside each repo. Your project CLAUDE.md should explain the tech stack, folder structure, commands, deployment steps, and project rules. You can also add project-specific skills and agents there. And this is the key: if you install a skill inside one project, it will not appear in your globals. For habits, project is for context. If you vibe code and I'll send you my ultimate