● OPERATING CREW

Let’s get your
AI setup working.

Bring your conversations and project context together, so the next step is easier to see—and shared work stays in one place.

Start the setup
The idea
Your information. Your system.Shared project context can flow to the team’s existing cards, and your assistant can read your shared packaging work. Your other work stays in your own workspace.

From conversations to action

The intended flow. The setup steps below test each connection before we depend on it.

Your sources

Email accounts, existing labels and—where accessible—WhatsApp and texts.

Your system

Supabase holds source records, people, supplier relationships and your confirmed context.

Shared handoff

Agreed labels and review rules select relevant work. Unclear matches wait for review.

One project card

Team facts and next steps reach the existing Atlas card, where everyone sees the same work.

Back to you: Atlas packaging cards and actions → your Claude → one combined view with your own projects. Your confirmed corrections and work updates flow back through Atlas’s supported write path. This connection is part of the setup and must be verified.
Example: a supplier answers a quote request → the project label and thread provide context → the response is matched to the right project → a review-ready handoff appears. No message is sent without your approval.

How labels and context work

Keep using the labels you already have. The setup will discover them and suggest a mapping for you to confirm.

Email labels

Labels are clues, not the whole answer.

A brand label can mark a conversation as eligible for team sharing. The system still checks the message and project context.

Brand label     Project match

One supplier, several projects? A supplier can quote for multiple brands. A single thread can mention more than one project.

Confirm a mapping from existing labels. An explicit private label takes priority; a new or unclear label waits for review.

Your knowledge

Fill in what the emails can’t say.

The system proposes a map of manufacturers, contacts, customers and projects. You can correct or add the missing relationships by speaking.

“Which projects does this supplier support?”

Dictate an answer with your usual tool. Review the proposed interpretation, then save it as reusable context with its source and date.

Later, call recording can be explored separately. It is not part of the first setup.

Set it up with Claude

Work through the steps in order. Open each prompt, copy it into Claude Code, and let Claude do the work. It should ask only when you need to sign in or choose something.

1
Start here

Inspect and connect your workspace

Find your existing Supabase project, tables and 1Password connection; avoid rebuilding what already works.

Done when: You can tell which project, existing tables and connections are working.
View prompt
Help me set up my own AI workspace for packaging projects. First inspect what I already have on this Mac: the workspace, Supabase organization and project, existing tables and data, 1Password connection, tools, code, and any scheduled ingestion jobs. I may have already created tables. Reuse working components, preserve existing records, and do not create a second Supabase project or clone another system's schema by default.

Connect to 1Password and my existing Supabase project using supported tools. Ask me only for required sign-in or authorization. Never ask me to paste or print a password, API key, token or database connection string into chat, logs or code. Keep privileged credentials on trusted systems.

Report the project name and reference, existing schema and which connections you verified. Distinguish the Supabase dashboard membership, publishable key, secret key and database connection by what each actually permits. Do not claim an integration works without testing it. Do not send messages or change external access in this step. Complete all available work and tests, and tell me only the exact sign-in or decision you need from me.
2
One-time access

Give Yan access

Give Yan the administrative access needed to troubleshoot the project and maintain the integration.

Done when: Yan has an invitation; acceptance and a successful access test are tracked separately.
View prompt
I want Yan to have Administrator access to my Supabase project for setup and troubleshooting. Prepare an invitation for yan@operatingcrew.com using Supabase's supported team-access flow. Prefer project-scoped Administrator if my plan supports it. If access must be organization-wide, show me which organization and projects it covers before I approve the invitation. Keep me as owner; do not transfer ownership.

Guide me through any required sign-in or confirmation and verify whether the invitation was sent. Tell me separately whether it has been accepted and whether Yan's access has actually been tested. Give me the project name and project reference to share with Yan. Never paste, email or print a secret key. If a separate integration credential is needed, describe a secure individually provisioned or 1Password sharing method. Finish the access setup as far as my authorization and the available tools permit.
3
14-day starting window

Connect your conversations

Connect both email accounts and test what is accessible from WhatsApp and Google Messages on this Mac.

Done when: A source-by-source report of what was read, what can sync, and what still needs pairing or access.
View prompt
Connect my Operating Crew email and my Packaging Network email; inspect the actual account addresses and providers and ask me to sign into or authorize each. Use supported read-only access; never send messages automatically. Inspect the Google Messages / SMS experience I use with my Pixel and the WhatsApp app or web session available on this Mac. Determine which messages, conversations, participant identifiers, timestamps, history and ongoing change feeds are actually accessible. Ask me to pair or authorize a device if required. Do not assume an API, local database or ongoing sync exists; test it.

With my authorization, start with the last 14 days for each connected channel, counting the available messages first. If older messages in the same thread are essential context, retain them separately as context rather than reporting them as new work. Import the supported sources into my existing Supabase using safe, resumable account/channel-specific cursors and idempotent identifiers. Preserve author, participants, timestamp, source/channel, message/thread ID and a link or reference to the original where available. Use incremental updates after initial capture and do not repeatedly read or reprocess unchanged messages. Reuse existing data and jobs.

For email, keep provider/account message IDs and the original RFC Message-ID header. Use verified Message-ID plus sender and other envelope checks to recognize a message in multiple inboxes, retain each mailbox's receipt and labels, and extract it once; do not use similar text, subject or timestamp as unique proof. If the other copy exists but has not been processed, keep it eligible for processing; hold ambiguous or conflicting identity. Never assume Atlas can access my other email account. Strip repeated quoted history from fact extraction while keeping enough context. For text and WhatsApp use reliable native message IDs if available; never collapse separate messages merely because their text is similar.

Report exact source coverage, initial message counts, deduplicated copies, incomplete history, ongoing sync behavior and any pairing or access gaps. Test a real small set and an unchanged repeat. Do not ingest or set up call transcripts for now. Complete the work available and state any input only I can provide.
4
Use your existing labels

Map labels to shared work

Tell the system which existing brand labels may contribute to shared work; select the exact project using context.

Done when: Your labels are inventoried and mapped without treating a supplier or company as a single project.
View prompt
Inspect my existing email labels across the connected accounts and propose a small mapping for me to review rather than inventing a new taxonomy. Store the source account, provider label ID, label name, whether the label is eligible for Operating Crew sharing, associated company and optional project, and a mapping status. Preserve label IDs across renames. New or unclear labels should need mapping. Ask me to confirm which labels represent shared OC brands or work and which are independent or explicitly private. An explicit private rule takes precedence over a shared label.

My own workspace may ingest sources I authorize; labels and agreed rules decide what is eligible for the shared handoff. A brand label is a clue, not by itself proof of a specific project. One supplier can work on multiple clients and projects; one client project can have multiple suppliers; one thread can discuss multiple projects. Use labels, exact thread and participant context, and existing eligible shared-project context to assign facts to a project. Mark ambiguous items for review rather than forcing them onto a card. Revisit affected items when labels or underlying messages change.

Prepare a small, versioned and documented handoff in my existing Supabase that Yan's connector can read: stable source/message and revision IDs, timestamps, labels, project hints, approved context, eligibility, acknowledgments and error/retry status. Keep my independent data in my workspace. Do not directly change Atlas unless the appropriate connection and integration contract are provided and agreed. Test a known shared label, an unrelated label, a private override, and an ambiguous project. Complete the mapping and testing with me using actual label names.
5
Packaging access

Connect shared Atlas work

Connect your Claude to the team’s shared packaging work, with access limited to the right projects.

Done when: Your assistant can read the authorized packaging view and has a supported path to record updates.
View prompt
Help me connect my Claude workspace to Operating Crew’s existing Atlas system for shared packaging work. I need to ask for my open packaging tasks, view the existing project cards, and record source-backed facts, corrections and next steps when authorized.

First inspect the connections and documentation actually available to me. Work with Yan to obtain an individual, revocable connection scoped to shared packaging projects and the necessary packaging operations. Do not ask for or expose an OC service-role key, broad raw database access, personal tasks, credentials or non-packaging projects. Do not assume dashboard access is the same as database or assistant access.

Use Atlas’s supported project, fact, and obligation read/write interfaces. If those are not yet available, document the exact read and write operations, identity, scope and secure connection Yan needs to set up; prepare my side without claiming the connection works. Do not create new Atlas tables, independently grant yourself access or bypass the existing action and fact lifecycle. When an approved project has multiple suppliers, preserve each supplier’s distinct quote, owner, date and next action.

With the authorized connection, test one allowed packaging card and Justin-owned task, and verify that an out-of-scope project is not accessible. Record a harmless real correction only if an appropriate example exists; otherwise use the supported rollback or test path. Do not send external messages. Report the actual access, readback and any precise input required from Yan. Complete all available setup and verification.
6
Work together

Teach it your relationships

Use your voice to confirm the supplier and project map; save the context to your workspace and send authorized packaging context to Atlas.

Done when: A reviewed, source-backed map plus a verified path for corrections to shared packaging projects.
View prompt
Using the email, WhatsApp, text and shared Atlas context I have authorized, assemble an initial evidence-backed map of manufacturers, people and contact details, client brands, specific projects, supplier workstreams and supported capabilities. First inspect existing records and reuse them. Distinguish suggested from confirmed relationships and quote, sample, selected or inactive states when supported. Link each suggestion to its source and date; never infer the project from a manufacturer alone.

Present a short, voice-friendly review grouped by manufacturer and project. I use Wispr Flow: let me dictate naturally and answer several numbered questions at once. Show what you understood before saving, preserve my original dictated text as the source, and let me correct names or relationships. Save confirmed relationships and context in my Supabase with source, date and correction history. My independent projects remain there. Call recording and transcript ingestion are later work; for now I may dictate facts I learned during a manufacturer call.

For an OC packaging project, connect the confirmed work fact, person, project and supplier to the existing shared Atlas packaging card through its authorized integration and existing fact and obligation writers. Preserve exact project, time and source; keep unresolved or private details out of team views. If I correct stale card information, update the existing source-backed fact or action through the supported lifecycle, preserving history and other owners’ work. Do not create a duplicate card, fabricate completion or write directly to raw database tables. A confirmed supplier call detail may be recorded from my dictated note without claiming a call transcript exists.

Use my authorized packaging-scoped Atlas connection; do not request a broad OC service-role key or access to unrelated private data. If the supported connection or write path does not yet exist, prepare and test my side and provide Yan with the precise non-secret integration requirements. Do not say the shared card was updated until its actual readback confirms it. Verify one real project and one correction or a safe rollback test. Complete all setup and verification that access permits.
7
Work together

Run your work from one conversation

Ask Claude for your combined plate and keep shared packaging actions current in Atlas.

Done when: A tested combined task view, correct project card and source-backed update, with the same authoritative OC action on both sides.
View prompt
Set up and test my daily working workflow. When I ask “What is on my plate?”, read current Justin-owned work from the authorized shared Atlas packaging surface and my independent project system, covering all active tasks, distinct waits and follow-ups. Give me one numbered view, with clear shared and independent sections; deduplicate by linked authoritative task identity, not similar wording, and retain project, owner, status, due date, source and genuine dependencies. Do not mix other people’s tasks into mine; if source access or pagination fails, say what is missing instead of calling the list complete. Let me dictate numbered updates and handle independent items in parallel where the tools support it.

For each shared packaging project, show manufacturer workstreams independently: supplier/contact, item requested, quote or sample status, who owes the next step, promised date, whether a supplier response has arrived, whether I need to review it or pass it to the brand, and supporting source. Preserve multiple simultaneous quotes and waits. Unknown information stays unknown.

Test the end-to-end shared workflow on a real project I choose: read the existing card and canonical actions; compare one source-backed email or my confirmed dictated manufacturer-call note with the current card; through the authorized Atlas front door, record a supported new fact or correct a stale one and update the same authoritative next action if evidence supports it. Show actual card and task readback. Use a safe rollback test when the real situation has no appropriate update; never mark an incomplete action done or create an unnecessary duplicate. Record source identity and correction history.

When a supplier answer needs to be passed to a brand, show the evidence and prepare a draft for my review. Do not send any email or message without my explicit approval. Keep my independent projects in my own system while combining their tasks with my Atlas items in the conversational view.

Verify the project-specific packaging-only permissions using an allowed shared-project operation and a denied out-of-scope read/write; do not use a broad OC database service key. If the connector, authorized scope or lifecycle writer is not available, complete my side and give Yan the concrete non-secret contract and missing authorization; label all proposed features clearly, do not claim they work. Report actual results, card/action readback, access status, holds and any input only I can provide. Do the work fully until the working result or that specific input is reached.

A clearer start to the day

Once the connections are working, the same information can support a conversational work review and a project view.

The daily question

“What’s on my plate?”

See your next steps, what’s waiting on someone else, and which replies or supplier responses are ready for review. Work through a numbered list by voice.

By project

One row for each supplier

What was requested, who owes it, when it’s expected, and whether a response needs to be passed to the brand.

Start small: the first test is a 14-day window across the sources you choose. Test access to messages; don’t assume every channel supports the same connection.
A setup guide for working together. No account data is stored on this page.