Team Patterns

When your whole team uses Claude Code, standardize for consistency.

What to Share

1. CLAUDE.md Files

Commit to repo - everyone gets the same context:

git add CLAUDE.md .claude/
git commit -m "Add Claude Code configuration"

2. Custom Slash Commands

Share team workflows:

• Directory.claude/

  • Directorycommands/

    • review.md (code review)
    • deploy.md (deployment checklist)
    • onboard.md (new dev setup)

3. Skills

Domain-specific expertise:

• Directory.claude/

  • Directoryskills/

    • Directoryour-api-patterns/

      • SKILL.md
    • Directoryour-testing-standards/

      • SKILL.md

Team CLAUDE.md Template

# [Project Name]

## Team
- Tech Lead: @username (architecture decisions)
- On-call: Check #team-oncall Slack

## Quick Commands
- `make dev` - Start development
- `make test` - Run tests
- `make deploy-staging` - Deploy to staging

## Architecture
[Brief description of architecture]

## Coding Standards
- All code must have tests
- Use conventional commits
- PRs require 1 approval

## Current Sprint
- [ ] Feature X (owner: @alice)
- [ ] Bug Y (owner: @bob)

## Off Limits
- `infrastructure/` - Managed by DevOps team
- `legacy/` - Deprecated, being removed Q2

Onboarding Pattern

Create an onboarding command:

.claude/commands/onboard.md

Help onboard a new team member:

1. Explain the project structure
2. Walk through key files and patterns
3. Show how to run the development environment
4. Explain our testing approach
5. Point out where to find documentation
6. Suggest first good issues to tackle

Be welcoming and thorough.

New team member runs:

> /onboard