SLW / devportal
@teammate
Welcome

Pick a project — set it up once in Claude Desktop.

Each project runs in a cloud workspace with the app and dev database ready. You reach it through the Claude desktop app — no browser editor, no local setup — and build by describing what you want. Production data never reaches you.

First-time login

Start here — how it works, and your setup.

Everything you need to go from zero to shipping. Read how it works, do the one-time setup, connect your first project — then you're working. About 10 minutes the first time; seconds every day after.

1

How it all works

The Codespace is your environment — a cloud computer with the app running. Claude Desktop is your interface — you connect it to that workspace and build by talking. Nothing runs on your laptop; production data never reaches you.

01

One link, one sign-in

Open rivent.dev and sign in with your @slw.vc email. Bookmark it — it's the front door to every project.

02

A Codespace is your environment

GitHub builds a cloud workspace from the repo's .devcontainer — dependencies and dev-database wired up, identical for everyone. It runs on practice data; production is never injected. You never open the browser editor — you reach the workspace through Claude Desktop.

03

Claude Desktop is your interface

The native Claude app connects to that workspace over SSH. You get the Claude interface, with the real running environment behind it — one place to work.

04

Build by describing

Tell Claude what you want in plain English. It runs inside the Codespace — sees the real code, runs the app, uses the dev database.

05

Reviewed & persistent

Changes are reviewed before they go live, and the workspace persists — reconnect tomorrow right where you left off.

Stays open while
You're working
Idle-suspends after ~30 min, resumes on reconnect.
Compute cost
~$0.18 / hr
Billed to the org only while active. Auto-suspends.
Your Claude plan
Separate bill
You sign into Claude Desktop with your own account.
2

Set up your machine

Once per computer

Install two tools

~5 minutes, one time ever
1

Install the GitHub CLI & sign in

This lets your computer open cloud workspaces. In Terminal:

$ brew install gh
$ gh auth login

Choose GitHub.com → HTTPS → login with a browser. If you ever hit a "codespace scope" error, run gh auth refresh -h github.com -s codespace.

2

Install Claude Desktop & sign in

Download the Claude desktop app and sign in with your own Claude plan (Pro or Max). This is your interface for every project.

3

Open a project & connect Claude

Do this once per project. Already set up your machine (blocks 1–2)? Those are done forever — start right here for each new project. Setting up a second project just adds it alongside the first in your Claude Desktop dropdown.

For each project

Three steps, first time only

3

Create your cloud workspace

Pick your project and run the command in Terminal — it spins up the workspace (~30–60s the first time) with the app, dependencies, and dev database ready. No browser editor opens; you'll reach it through Claude Desktop.

Project: 
$ gh codespace create -R rivent-dev/LPCRM3
4

Register the workspace for Claude

One command tells your machine how to reach it, and shows its address:

$ gh codespace ssh --config >> ~/.ssh/config
$ gh codespace list # note the name, e.g. solid-parakeet-…

Your workspace address is cs.<that-name>.main — you'll paste it next.

5

Connect it in Claude Desktop

Click the "Where Claude runs" dropdown (bottom of the Code window) → + Add SSH connection, and fill in the four fields:

highlighted = what you type indashed = swap in your own value
Name
LP FlowAnything you like — just a label for this connection.
SSH Host
cs.your-workspace.mainfrom Step 4the name gh codespace list printed — written as cs.NAME.main.
Port
leave emptyNothing to enter — filled in automatically.
Identity
/Users/you/.ssh/codespaces.autofrom Step 4your Mac username in place of yough created this key for you.

Select the connection — Claude installs itself on the workspace (~20s). The dropdown now shows LP Flow instead of "Default."

4

Then, every day

6

Describe what you want, in plain English

Claude runs inside the workspace — it sees the real code, can run the app on the dev database, and makes the change. Your work goes up as a reviewed change; nobody edits the live app directly.

LP Flow › Add a "last contacted" date to the investor list and sort by it.

Coming back later? Open Claude Desktop → pick the project from the dropdown → keep going. No setup — it's already connected.

💡
You won't need to type paths. Each workspace opens straight in its project folder, so Claude is ready the moment you connect.

That's it — you're set up.

Everything after today is: open Claude Desktop, pick your project, build.

Coming soon

The project board — how work gets tracked & shipped.

Every change lives on our GitHub Project board, from a rough idea to a shipped feature. This is a first draft of how we'll use it.

🚧 Not live yet

The flow below is a draft preview — the columns and process aren't finalized. This tab lights up once it's set.

1

Where the board lives

All projects share one GitHub Projects board. Open it from any project card (Project board →) or bookmark it directly. Each card on the board is one piece of work — a fix, a feature, or an idea — and it moves left to right as it progresses.

Open the board ↗

2

The columns

📥

Inbox

Raw ideas and requests, unsorted. Anyone can drop one here — a sentence is enough.

📋

Up next

Triaged and ready to pick up, roughly in priority order.

🔨

In progress

Being worked on right now — a branch is open and Claude is on it.

👀

In review

A pull request is open, waiting for a teammate to approve.

Shipped

Merged and live. The card links to the PR that delivered it.

3

How an idea becomes a feature

1

Capture the idea

Add a card to Inbox — or use /capture while working and Claude files it for you.

2

Pick it up

Move a card to In progress, open the project in Claude, and describe what you want.

3

Open a pull request

Claude does the work on a branch and opens a PR — the card moves to In review.

4

Review & ship

A teammate approves, CI passes, it merges — the card moves to Shipped.

📝
Placeholder draft. The columns, labels, and exact flow aren't final — tell me what the board should actually track and I'll shape this into the real guide.