Onboard
Explains this repository's shared Claude Code setup to a new teammate, covering what is...
Install
npx skills add wesammustafa/Claude-Code-Everything-You-Need-to-Know --skill onboard -g -a claude-code -y- Repository
- wesammustafa/Claude-Code-Everything-You-Need-to-Know3.5k
- Category
- AI and agents
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 297 tokens
- Runs scripts
- No, instructions only
What it does
Explains this repository's shared Claude Code setup to a new teammate, covering what is committed and shared, what stays personal, and what the team-kit plugin adds. Use when someone asks how the team's Claude Code setup works or what they get by cloning the repository.
Explain this repository's shared Claude Code setup to a teammate who has just cloned it. Read files only; don't change any.
- Read the shared setup, skipping any file that doesn't exist:
.claude/settings.json: permissions, hooks, and the marketplaces and plugins it turns on;CLAUDE.mdand the files in.claude/rules/: the project's instructions to Claude;.claude/skills/and.claude/agents/: project skills and subagents;.mcp.json: project MCP servers;- each marketplace that
.claude/settings.jsondeclares by a local path, and the skills and agents of the plugins it lists.
- Name the personal files, which each teammate keeps out of the repository:
.claude/settings.local.json,CLAUDE.local.mdand the user folder~/.claude/. Don't open them. Say whether the repository's.gitignorelists the first two. - Report in three short sections: Shared with the team, Personal to you, and Added by team-kit. Give each file one line on what it does for the teammate. If a file you expected is missing, say so rather than guess what it would hold.
Keep the report short and concrete: file names and what each one changes, no general advice.
