Skip to content

Team Onboarding

This guide helps you get new team members set up with the toolkit and aligned on shared standards.

What Each Team Member Needs

  1. Claude Code CLI — npm install -g @anthropic-ai/claude-code
  2. Claude Code subscription — Active Anthropic account with Claude Code access
  3. Toolkit repository — Cloned locally
  4. Setup completed — scripts/setup.sh --full (or Windows equivalent)

Onboarding Checklist

1. Clone and Install

Have the new team member follow the Installation guide for their platform:

  • macOS/Linux: scripts/setup.sh --full
  • Windows: Git Bash with symlinks, PowerShell with junctions, or WSL (see Windows installation)

2. Verify the Setup

scripts/setup.sh --verify

All checks should show [OK]. If there are errors, re-run scripts/setup.sh --full.

3. Confirm Skills Load

Start Claude Code in any project and check that skills are available:

/0-start

If the skill isn't recognized, check:

  • Symlinks are healthy: ls -la ~/.claude/skills/
  • No unrecognized frontmatter fields in SKILL.md files (see Troubleshooting)

4. Review the CLAUDE.md Standards

The toolkit deploys a shared ~/.claude/CLAUDE.md with team-wide rules:

  • Scope discipline — only modify what's requested
  • No assumptions — ask for clarification
  • No placeholders — use real values or ask
  • Branch-based Git workflow — never commit to main directly
  • Security standards — no secrets in code

New team members should read through this file to understand the shared expectations.

Keeping the Team in Sync

After Toolkit Updates

When the toolkit repository is updated (new skills, agents, or config changes):

cd V025-claude-toolkit
git pull
# Symlinks auto-update — no re-install needed

If new skills or hooks were added (new manifest entries), re-run: 

scripts/setup.sh --full


cd V025-claude-toolkit
git pull
# Directory junctions auto-update for existing skills

For new skills/hooks, re-run the PowerShell setup steps from the Windows installation guide.

cd V025-claude-toolkit
git pull
scripts/setup.sh --full   # or scripts/install.sh

Copy installs always need a re-run after pulling changes.

Checking for Drift

To see if a team member's local config has drifted from the golden copies:

scripts/setup.sh --diff

This compares ~/.claude/CLAUDE.md, settings.json, and other config files against the repository's golden copies in configs/user-global/.

Platform-Specific Notes

Windows Team Members

  • Recommend Git Bash with symlinks enabled for the closest experience to macOS/Linux
  • If symlinks aren't possible, directory junctions work for skill directories without admin rights
  • File-level symlinks (hooks, commands) require Developer Mode — if that's not available, use copies and re-run setup after each git pull
  • See the full Windows installation guide for details

Mixed Teams (macOS + Windows)

The toolkit works identically across platforms once installed. The only difference is the installation method. All skills, agents, commands, and hooks are platform-agnostic markdown and shell scripts.

Shell scripts in hooks

Hook scripts (.sh files) run in Bash. On Windows, Claude Code uses Git Bash or WSL to execute them. Ensure one of these is available.