56 lines
2.0 KiB
Markdown
56 lines
2.0 KiB
Markdown
# Welcome to Whisper Money
|
|
|
|
## How We Use Claude
|
|
|
|
Based on Víctor Falcón's usage over the last 30 days:
|
|
|
|
Work Type Breakdown:
|
|
Debug Fix ████████████████████ 100%
|
|
|
|
Top Skills & Commands:
|
|
/sentry-cli ████████████████████ 1x/month
|
|
|
|
Top MCP Servers:
|
|
_None used in this window_
|
|
|
|
## Your Setup Checklist
|
|
|
|
### Codebases
|
|
- [ ] whisper-money — https://github.com/whisper-money/whisper-money
|
|
|
|
### MCP Servers to Activate
|
|
- [ ] _None required yet_ — the team hasn't leaned on MCP servers in this window. Sentry access is via the `/sentry-cli` skill (see below).
|
|
|
|
### Skills to Know About
|
|
- [ ] `/sentry-cli` — drives Sentry from the command line (view issues, events, projects, orgs, make API calls). The team uses it when triaging and fixing flagged errors before opening a PR.
|
|
|
|
## 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. -->
|