DeltaForceOS Beginner Curriculum
/ LESSON 04 · 50m

Daily Operator Setup

/ Curriculum notes

This lesson is available as written curriculum now. Use the notes below with the matching PDF workbook in the resources library.

Accounts, keys, folders, and your first repeatable routine Workbook: /resources/daily-operator-build-guide.pdf Codex route: /resources/daily-operator-codex-build-guide.pdf Claude Code route: /resources/daily-operator-claude-code-build-guide.pdf

/ Choose your build route

Build this lesson inside Codex

Open the repo in Codex, let it inspect the files, then paste the prompt. Ask it to edit only the smallest set of files and verify before you deploy.

Before Codex
1. Open the project in Codex.
2. Confirm .env.local exists locally and is ignored by Git.
3. Open README.md and package.json so Codex can orient itself.
4. Do not paste private keys into the prompt.
Paste this prompt
Inspect this repo for the Daily Operator Setup build.

Outcome:
Have a clean workspace that can safely run your first real automation every morning.

Tools:
Skool, GitHub, Supabase, Vercel, Resend, Telegram, PostHog, 1Password

Explain the files a beginner needs to understand before editing:
README.md, package.json, src, public, scripts, .env.local, and any Supabase files.

Then implement the smallest safe version, list required env names, run the build or focused tests, fix failures, and summarize changed files.

/ Transcript

Daily Operator Setup Outcome: Have a clean workspace that can safely run your first real automation every morning. Tools: Skool, GitHub, Supabase, Vercel, Resend, Telegram, PostHog, 1Password Workbook: /resources/daily-operator-build-guide.pdf Codex route PDF: /resources/daily-operator-codex-build-guide.pdf Claude Code route PDF: /resources/daily-operator-claude-code-build-guide.pdf Build assignment: Ship a daily brief that writes one row to Supabase and sends one message to either email or Telegram. Use the lesson tabs to choose Codex or Claude Code, then post the proof in Skool.