Set a config baseline for your team

When several people share a project, "it works on my machine" is a real risk. A clear scope baseline fixes that.

1. Decide what belongs at project scope

User-scope assets are personal; project-scope assets ship with the repo and apply to everyone. Put shared conventions, skills, and MCP servers at project scope so the whole team inherits them.

2. Import shared instructions

A project CLAUDE.md can import shared files via @path (for example, importing AGENTS.md). Berth resolves the import chain so you can confirm everyone actually receives the same instructions.

3. Verify with health checks

Before sharing, run through Berth’s health checks: missing imports, broken paths, and conflicting scope definitions all show up here. Fix them once, and the team starts from a known-good baseline.