# Welcome to MovieDice

## How We Use Claude

Based on User's usage over the last 30 days:

Work Type Breakdown:
Plan / Design ██████████░░░░░░░░░░ 50%
Build Feature ████░░░░░░░░░░░░░░░░ 21%
Debug / Fix ███░░░░░░░░░░░░░░░░░ 14%

Top Skills & Commands:
/usage ████████████████████ 14x/month
/clear ██████░░░░░░░░░░░░░░ 4x/month
/effort ██████░░░░░░░░░░░░░░ 4x/month
/model ████░░░░░░░░░░░░░░░░ 3x/month
/remote-control ████░░░░░░░░░░░░░░░░ 3x/month
/permissions ████░░░░░░░░░░░░░░░░ 3x/month
/batch ███░░░░░░░░░░░░░░░░░ 2x/month
/compact ███░░░░░░░░░░░░░░░░░ 2x/month

Top MCP Servers:
_None configured_

## Your Setup Checklist

### Codebases

- [ ] moviedice — https://gogs.altsol.dev/claude/moviedice

### MCP Servers to Activate

- [ ] _None configured for this team_

### Skills to Know About

- `/usage` — check your Claude usage / quota. The team checks this often.
- `/effort` — adjust how much thinking effort Claude spends on a task.
- `/model` — switch between Opus / Sonnet / Haiku for the current session.
- `/remote-control` — drive Claude Code from another device or session.
- `/permissions` — review and edit what Claude is allowed to do without prompting.
- `/batch` — queue up multiple prompts to run in sequence.
- `/compact` — compress conversation history when context gets long.
- `/clear` — start a fresh conversation when switching tasks.
- `@pm` — invoke the PM agent for project-status questions ("where are we?", scope checks, feature feasibility). Used heavily on this project.

## 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. -->