GuidesTeam Setup

Team Setup

Set up Claude Code Setup for your team with shared standards and modules.

Overview

Teams can share:

  • Coding standards - Company-specific conventions
  • MCP servers - Internal tools
  • Workflows - Team processes

Create a Custom Module Repository

mkdir company-claude-modules
cd company-claude-modules
git init

Structure

company-claude-modules/
├── VERSION              # e.g., "1.0.0"
├── CHANGELOG.md
├── skills/
│   ├── company-standards/
│   │   └── SKILL.md
│   └── internal-api-guide/
│       └── SKILL.md
└── mcp/
    └── internal-search.json

Example Skill

---
name: company-standards
description: ACME Corp coding standards
type: context
applies_to: [python, typescript, javascript]
---
 
# ACME Corp Coding Standards
 
## Logging
 
Always use structured logging:
\`\`\`python
logger.info("user_action", user_id=user.id, action="login")
\`\`\`
 
## Error Handling
 
Wrap external calls in try/except with specific exceptions.
 
## API Design
 
- Use snake_case for JSON fields
- Version APIs with /v1/, /v2/ prefixes
- Return ISO 8601 timestamps

Push to Company Git

git add .
git commit -m "Initial custom modules"
git remote add origin git@company.com:team/claude-modules.git
git push -u origin main

Team Installation

Each team member runs:

/add-custom git@company.com:team/claude-modules.git

This:

  1. Clones the repository
  2. Installs skills and MCP servers
  3. Overrides built-in modules with same names

Keeping Updated

When you update the custom modules:

  1. Push changes to the repository
  2. Bump VERSION
  3. Update CHANGELOG.md

Team members update with:

/claude-code-setup

Claude will detect the new version and offer to update.

Solo vs Team Mode for Projects

When setting up individual projects, team members choose:

ModeCLAUDE.md
SoloPersonal, not shared
TeamTracked in Git, shared

Team mode is useful when:

  • Multiple developers work on same project
  • Project handoffs are common
  • You want shared context

Related

Session WorkflowCreating Skills