Getting set up

You haven't needed this yet — you've been focused on design. This is for whenever you first open Claude Code to work on Allin directly: what to do, and the one rule that matters.

Two things to do

1. Accept the GitHub invite for allin-backend (check your email, or github.com/Maelwi/allin-backend/invitations) — you already have access to allin-ios and App Store Connect.
2. Open Claude Code and point it at whichever repo you're working in — allin-ios for anything app-facing, allin-backend for anything server-side. It'll clone the repo the first time you ask it to, and it automatically picks up that repo's CLAUDE.md — the same context and rules this session has. You don't need to touch git or the terminal yourself; you just tell Claude what you want changed, same as here.

If you want your own Claude to see Allin's Amplitude data

1. Marie invites you to Allin's Amplitude org (join-allin-253655) — check your email for the invite and accept it. This step is hers to do, not yours; she's an org admin there, you aren't yet.
2. In your own Claude Code, go to Settings → Connectors → add Amplitude, and log in with the account you just accepted the invite with. Once connected, your own Claude sessions can query Allin's Amplitude data directly, the same way this session can for other projects.

The one rule that matters

Nothing goes live — no push, no deploy, no App Store submission, no shipped copy — until you and Marie have both said yes to that specific change. Building and reviewing locally is always fine and doesn't need to wait for that. Both repos' CLAUDE.md already say this; it's here too because it's the one thing worth knowing before you start.