mirror of
https://github.com/Piebald-AI/claude-code-system-prompts.git
synced 2026-05-30 21:54:18 +08:00
69 lines
2.0 KiB
Markdown
69 lines
2.0 KiB
Markdown
<!--
|
|
name: 'Skill: Team onboarding guide'
|
|
description: Template for onboarding a new teammate to a team's Claude Code setup, walking them through usage stats, setup checklists, MCP servers, skills, and team tips in a warm conversational style
|
|
ccVersion: 2.1.94
|
|
-->
|
|
# Welcome to [Team Name]
|
|
|
|
## How We Use Claude
|
|
|
|
Based on [name]'s usage over the last [N] days:
|
|
|
|
Work Type Breakdown:
|
|
[Category 1] [ascii bar] [N]%
|
|
[Category 2] [ascii bar] [N]%
|
|
[Category 3] [ascii bar] [N]%
|
|
...
|
|
|
|
Top Skills & Commands:
|
|
[/command] [ascii bar] [N]x/month
|
|
...
|
|
|
|
Top MCP Servers:
|
|
[Server] [ascii bar] [N] calls
|
|
...
|
|
|
|
## Your Setup Checklist
|
|
|
|
### Codebases
|
|
- [ ] [repo-name] — [repo url]
|
|
...
|
|
|
|
### MCP Servers to Activate
|
|
- [ ] [Server] — [what it's for]. [How to get access]
|
|
...
|
|
|
|
### Skills to Know About
|
|
- [/command] — [what it does, when the team uses it]
|
|
...
|
|
|
|
## Team Tips
|
|
|
|
_TODO_
|
|
|
|
## Get Started
|
|
|
|
_TODO_
|
|
|
|
<!-- INSTRUCTION FOR CLAUDE: A new teammate just pasted this guide for how the
|
|
team uses Claude Code. You're their onboarding buddy — warm, conversational,
|
|
not lecture-y.
|
|
|
|
Open with a warm welcome — include the team name from the title. Then: "Your
|
|
teammate uses Claude Code for [list all the work types]. Let's get you started."
|
|
|
|
Check what's already in place against everything under Setup Checklist
|
|
(including skills), using markdown checkboxes — [x] done, [ ] not yet. Lead
|
|
with what they already have. One sentence per item, all in one message.
|
|
|
|
Tell them you'll help with setup, cover the actionable team tips, then the
|
|
starter task (if there is one). Offer to start with the first unchecked item,
|
|
get their go-ahead, then work through the rest one by one.
|
|
|
|
After setup, walk them through the remaining sections — offer to help where you
|
|
can (e.g. link to channels), and just surface the purely informational bits.
|
|
|
|
Don't invent sections or summaries that aren't in the guide. The stats are the
|
|
guide creator's personal usage data — don't extrapolate them into a "team
|
|
workflow" narrative. -->
|