# ⚠️ DEPRECATED 2026-07-18 — Collins fired. Nothing in this directory is active. Do not send any drafts here.

# Collins — start here

Use this checklist to open the St. Pierre builder workspace, sign in to Claude Code, and verify your access.

## What Akash must unlock first

- Invite Collins's GitHub account to [`akashpunnoose0211/stpierre-builder`](https://github.com/akashpunnoose0211/stpierre-builder) with **Write** access.
- Put the Claude subscription on Collins's company email. Claude Code requires a paid Pro, Max, Team, Enterprise, or Console account.
- Invite Collins to the St. Pierre Slack workspace and these channels: `#client-onboarding`, `#call-ins`, `#daily-reports`, `#notes`, and `#documents`.
- Share only the St. Pierre Google Drive folders he needs.
- Provision every St. Pierre business tool on day one under Collins's own identity. Use normal production member/editor roles; never send a token in Slack, email, or a file.

## 1. Open the Codespace

**Collins must create his own Codespace while signed into the GitHub account tied to `alex@stpierre.ai`. Do not open or reuse Akash's existing Codespace. Codespaces belong to the account that creates them.**

1. Open a private/incognito browser window so Akash's GitHub session is not reused.
2. Sign into—or create—the GitHub account using `alex@stpierre.ai`.
3. From that account, accept Akash's repository invitation.
4. Open the [builder repository](https://github.com/akashpunnoose0211/stpierre-builder).
5. Confirm the top-right GitHub avatar belongs to Collins's account.
6. Click **Code → Codespaces → Create codespace on main**.
7. Wait for the browser editor to finish building. The setup installs Claude Code and the project tools automatically.

To reopen it later, Collins signs into his GitHub account, goes to [github.com/codespaces](https://github.com/codespaces), and opens his `stpierre-builder` Codespace. Akash's Codespace remains separate.

## 2. Prove the workspace is safe

In the terminal at the bottom of the Codespace, run:

```bash
bash .devcontainer/verify.sh
```

The required result is:

- project tasks are readable;
- the credential vault is blocked;
- the final line says `PASS — safe for a builder`.

Stop and report the exact red line if the vault is readable or the check fails. Do not work around it.

## 3. Sign in to Claude Code

In the same terminal, run:

```bash
claude
```

1. Choose the Claude subscription sign-in option.
2. Open the browser link.
3. Sign in with Collins's new company Claude account—not Akash's account.
4. Return to the Codespace after the confirmation page appears.

Verify the login and installation:

```bash
claude auth status --text
claude doctor
```

Claude is ready when the first command shows Collins's account and the health check has no blocking error.

## 4. Connect the full business stack

Do not copy Akash's personal connections. Collins signs in with his own company identity or invited user seat.

1. Open Claude in the browser.
2. Go to **Settings → Connectors**.
3. Connect every supported St. Pierre app using Collins's own company identity: Slack, Google Workspace, GitHub, GoHighLevel, Meta, n8n, Typeform, Cloudflare, Calendly, Canva, Loom, Instagram, YouTube, ManyChat, the publishing scheduler, and the approved research/media tools.
4. GitHub's connector is optional for normal code work because the Codespace already has repository access. It is useful for issues and pull requests.
5. Return to Claude Code and enter `/mcp`.
6. Confirm every expected connection is healthy and belongs to Collins—not Akash.

## 5. Use Composio as the day-one connection hub

Composio can simplify OAuth across many apps, but it does not grant permission by itself. Collins still needs his own user or invited seat in every app.

First create Collins's user/seat inside each business app. Then install Composio in Claude Code:

```text
/plugin marketplace add ComposioHQ/composio-plugin-cc
/plugin install composio-mcp@composio
/reload-plugins
```

Then connect every supported St. Pierre app with Collins's identity. Use direct Claude connectors where they are better; use Composio for the remaining apps. Avoid duplicate connections to the same account.

## Full day-one access

Provision normal production member/editor access to:

- GitHub builder repo and Codespace;
- Claude Code;
- the five Slack channels;
- St. Pierre Google Workspace and Drive;
- project/task data and the builder-safe database role;
- GoHighLevel, Meta Business/Ads, n8n, Typeform, Cloudflare, and Calendly;
- Canva, Loom, Instagram, YouTube, ManyChat, and the publishing scheduler;
- approved enrichment, AI, and media services used by assigned work.

“Everything” means full operational access to St. Pierre work. It does not mean Akash's personal accounts, owner/admin billing, raw credential export, the credential vault, banking/payment control, or personal finance data.

Access is not automatic authority to fire high-impact actions. Spending, outbound human messages, public publishing/launches, deletion, credential changes, and permission changes still stop at the written human gate.

## Definition of done

Onboarding is complete only when Collins posts this proof in `#daily-reports`:

- builder repo and Codespace opened;
- `verify.sh` passed and the vault was blocked;
- Claude Code shows Collins's account and passes its health check;
- the full expected app list appears in the access tracker and works under Collins's own identities;
- Composio and `/mcp` show healthy connections without duplicate accounts;
- GitHub branch creation works without pushing to `main`;
- no personal Akash login, raw token, owner billing control, or credential-vault access was used;
- first assigned ticket, next move, and any exact blocker are named.

Working rule: create one branch per ticket, make small named commits, push often, and open a pull request for review. Never work directly on `main`.

## Official help

- [Create a GitHub Codespace](https://docs.github.com/en/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository)
- [Install and authenticate Claude Code](https://code.claude.com/docs/en/installation)
- [Connect Claude Code to tools](https://code.claude.com/docs/en/mcp)