Settings, Rules, and Memory
Claude Code has several ways to control behavior and preserve context. The goal is not to memorize every option. The goal is to put guidance in the narrowest durable layer that fits the need.
Choose the right layer
| Mechanism | Use it for | Live workshop emphasis |
|---|---|---|
| Settings | Behavior, permissions, tool access, and defaults for a user or project. | Start with least privilege. Expand access only after the agent has earned trust for a broader scope. |
| Rules | Focused instructions that apply to a particular directory, file type, or area of the codebase. | Use scoped rules when guidance should not consume attention everywhere in the project. |
| CLAUDE.md | Durable project-wide context: mission, architecture, stack, commands, workflow, and testing expectations. | Keep it concise and operational. Import supporting guidance with @path/to/import when needed. |
| Auto Memory | Useful preferences and recurring context Claude learns while you work. | Treat it as personal assistance, not the authoritative source for team standards or critical project decisions. |
The live takeaway
Use settings for behavior and permissions, rules for scoped guidance, CLAUDE.md for durable project context, and Auto Memory for accumulated personal context.
- Put shared, consequential guidance in version-controlled project files.
- Prefer deterministic guardrails—permissions, hooks, tests, CI, and protected paths—when a rule must always be enforced.
- Review and correct stored guidance as the project changes.