Allin — internal
Enter the password to continue.
Isabel's Setup
Allin · for Isabel

Getting set up

Everything you already have access to, and the three things left to do to get your Claude Code terminal working the same way Marie's does.

What you already have

Supabase
Owner on the "Allin" organization — full access to the live database, project ref wsxpmcbtcknewpiwudsc.
allin-ios on GitHub
Write access already granted.
allin-backend on GitHub
Invite sent — accept it from your email or github.com/Maelwi/allin-backend/invitations.
App Store Connect
You're already the account holder — the highest access level there is. Nothing to change.

Three steps to get your terminal working

  1. Accept the GitHub invite for allin-backend, then clone both repos:
    gh repo clone Maelwi/allin-ios · gh repo clone Maelwi/allin-backend
  2. Link the Supabase CLI so you can query the database directly from your terminal, not just the dashboard:
    supabase login (your own browser login), then from inside your allin-backend clone: supabase link --project-ref wsxpmcbtcknewpiwudsc
  3. Nothing else to do — both repos already carry a CLAUDE.md at their root, so cloning gives every Claude Code session the same context this one has automatically: architecture, current state, and the one rule that matters most everywhere in this project — never touch anything that affects live users, live data, or production infrastructure until you and Marie have both explicitly said yes, for that specific change. The two blocks below are just for reference, in case you want to read them before cloning.

allin-ios/CLAUDE.md

Show the full file
Allin iOS — project brief for Claude Code

Allin is an audio "neural repatterning" wellness app: check in with what you're feeling, name the belief underneath it, listen to a science-backed audio session (memory reconsolidation / polyvagal / somatic protocols), reflect. Swift/SwiftUI, iOS only today.

Team: Isabel Lewren — CEO, owns design and user-facing copy. Marie Wistrand — CSO. Whoever is at the keyboard runs Xcode and builds — this file doesn't assume which of you that is.

Where things live
- This repo — GitHub Maelwi/allin-ios, live branch main. Both Isabel and Marie have write access.
- Backend repo — Maelwi/allin-backend (Supabase edge functions, migrations, seed scripts). Separate repo, not inside this tree — /add-dir it when a task needs it.
- Supabase — project ref wsxpmcbtcknewpiwudsc (us-east-1), owned by the "Allin" Supabase organization. Both Isabel and Marie are Owners on that org.
- App Store Connect — bundle com.allinwellltd.allin, app name JoinAllIn, Apple ID 6754271583, Team "Allin Well Ltd" 2L65759584, account holder isabel.lewren@gmail.com.
- Analytics — Segment ("Join-Allin-Isabel" workspace, source "Allin iOS") -> Amplitude (project 835236) + Customer.io (workspace 216147, EU region). Meta/Facebook SDK is separate, not routed through Segment.
- Deep links — https://link.join-allin.com/<path>, AASA on Cloudflare Pages ("allin-links" project). Push deep-linking needs v2.2+; email links work for everyone.

Secrets, API keys, and DB passwords are never written into this file or into memory — ask whoever holds them when a task needs one.

The gate — same rule for anyone working here
HARD RULE, above everything else: never touch anything that affects live users until Isabel or Marie has explicitly approved it, for that specific change. Covers pushing, deploying, merging to main, any live database write, anything through Customer.io, any App Store Connect action, and shipping any user-facing copy. "Keep working" authorizes local, committed, unshipped work — never the live step.

Proceed freely on: local code edits, local commits (not push), read-only queries against Supabase/Amplitude/Customer.io/Segment, drafting migrations without applying them, research and audits.

Copy approval: all Allin user-facing copy needs sign-off from both Isabel and Marie before it ships or sends.

Hard rules (each here because it went wrong once)
- Monetization code is deliberate design, not bugs. Read the surrounding code and git history before touching paywall / RevenueCat / StoreKit / entitlement logic.
- Don't break what already worked. Check recent git history before claiming a fix.
- Never bump min_ios_version until the new build is actually live on the App Store.
- Migrations in the repo may not match the live schema — several functions exist live but aren't tracked in supabase/migrations/. Check the live schema, don't trust the migrations folder blindly.

Verification norms
Observed behaviour, not "it compiles." A screenshot has to be looked at, not just taken. Partial coverage ("7 of 9 checked") is a defect list, not a pass.

allin-backend/CLAUDE.md

Show the full file
Allin backend — project brief for Claude Code

Supabase edge functions + migrations for Allin. Companion repo is Maelwi/allin-ios — see its CLAUDE.md for product/team/App-Store context; this file covers backend-specific facts only.

Team: Isabel Lewren (CEO) and Marie Wistrand (CSO) both have write access to this repo and are Owners on the Supabase org.

Where things live
- Supabase project — ref wsxpmcbtcknewpiwudsc (us-east-1), owned by the "Allin" Supabase organization.
- Edge functions — supabase/functions/. Tracked in git: recommend-plan, revenuecat-webhook, delete-user-data. Note: some functions are deployed live but NOT in this repo yet (a known drift issue) — check the live project's actual function list via the Supabase dashboard before assuming the repo is the full picture.
- Auto-deploy — GitHub Actions on push to main runs supabase functions deploy + reseeds audio_metadata.json.
- CLI auth — supabase login needs a real browser OAuth flow; it fails in a non-TTY shell.
- Docker is not guaranteed to be running — supabase db dump / db diff --use-migra may fail; prefer --linked flags or the Management API instead.

The gate — same rule as the iOS repo
HARD RULE, above everything else: never touch anything that affects live users until Isabel or Marie has explicitly approved it, for that specific change. Covers pushing to main (auto-deploys), any migration or write against the live project, setting/rotating secrets, and anything reaching a real user's data.

Local edits, local commits, branches, read-only queries, and drafting migrations without applying them: proceed freely.

Secrets are never written into this file, into memory, or hardcoded — they live in Supabase project secrets / GitHub Actions repo secrets and are read via Deno.env.get().