Loading
Coastal browser adventure / Game course
Tidelight.
Build a 3D browser game with AI, starting from nothing. You'll get an AI helper (Claude or ChatGPT), set up a Mac step by step, then follow the real Tidelight build, made with Codex, Blender and three.js in one afternoon, and make your own game alongside it. Short lessons, plain words, real prompts.
Actual browser-game capture / Browser demoWatch chapter 1, freeAn original game / By Jeffrey Oyeneye
What you build
A little delivery. A brighter harbor.
Get an AI helper and set up a Mac for building, even if you've never opened the Terminal.
Turn a game you like into your own one-page plan and a first playable version.
Polish it in rounds, and push back when the AI suggests the wrong thing.
Test it like a player and put it online with a link you can share.
Inside the course
Lesson by lesson.
37 lessons in 10 sections. The first 17 lessons are free with an account. The rest open with the course.
Start here0 / 3
- Free preview
Lesson 1: The whole build in a minute
Tidelight, from the first question to a live link, in one minute.
- Free preview
Lesson 2: What you'll make, and how this course works
What you'll build, what you need (nothing yet), and how each lesson works.
- Free preview
Lesson 3: The loop: you direct, the AI builds, you make it prove it
The working loop behind the whole course.
Get your AI helper0 / 4
- Free preview
Lesson 4: What an AI helper is, and which one to pick
Claude or ChatGPT: what they do, how they differ, and how to choose.
- Free preview
Lesson 5: Get Claude: the account and the app
Make a Claude account, install the Claude app, and find Claude Code inside it.
- Free preview
Lesson 6: Or get ChatGPT and Codex: the account and the app
Make a ChatGPT account and install the Codex app (what Tidelight used).
- Free preview
Lesson 7: Your first conversation
Talk to your AI helper before you build: ask it what it can do.
Your computer, explained0 / 3
- Free preview
Lesson 8: What the Terminal is, and how to open it
The Terminal is a window where you type instructions. Here's how to open it and what you'll see.
- Free preview
Lesson 9: Folders and paths, in plain English
Every file lives in a folder. A path is the address of a folder, written out.
- Free preview
Lesson 10: Your first command, and what an error looks like
Type a command, read the answer, and see that an error is just a message.
Set up the tools0 / 7
- Free preview
Lesson 11: Make your GitHub and Vercel accounts
GitHub keeps your code safe. Vercel puts your game online.
- Free preview
Lesson 12: Install Blender, and check it from the Terminal
Blender builds the 3D world. The AI drives it; you only install it.
- Free preview
Lesson 13: Install Node.js, and check it
Node.js runs the game while you build it, and runs its tests.
- Free preview
Lesson 14: Install Git, and tell it who you are
Git saves every version of your game, so you can always go back.
- Free preview
Lesson 15: Make your game folder, and open it in your AI app
One folder for your game, opened in Claude Code or Codex.
- Free preview
Lesson 16: Your first build prompt, and how to check it worked
Ask the AI to make one small file, approve it, and check it's really there.
- Free preview
Lesson 17: If setup goes wrong
The errors beginners hit most, and the fix for each.
Get the mockup first0 / 4
- Checking access
Lesson 18: Pick a game you like, and keep yours original
Learn from a game you admire without copying it.
- Checking access
Lesson 19: Ask for the mockup, not the game
Before any code: a one-page plan and one picture of the finished game.
- Checking access
Lesson 20: Write the mockup prompt
The real prompt behind Tidelight's mockup, part by part, and how to write yours.
- Checking access
Lesson 21: Approve the mockup, then decide how to build it
Say yes to the picture, then write down the few decisions that keep the game small.
The first playable0 / 4
- Checking access
Lesson 22: Let the AI build your world in Blender
Nobody modeled the harbor by hand. A script drives Blender and exports the world.
- Checking access
Lesson 23: See it in your browser
npm run dev starts your game on your own computer, at a local address.
- Checking access
Lesson 24: Tests that can fail
A test is a small check the AI writes. A test that never fails proves nothing.
- Checking access
Lesson 25: Play it, then save it
Play your first version to the end, then save it as your first commit.
Make it look good0 / 4
- Checking access
Lesson 26: How to say "not good enough"
Three short prompts drove three rounds of polish.
- Checking access
Lesson 27: Fix what's broken first
Round 1 started with a geometry bug, not a style problem.
- Checking access
Lesson 28: Add variety without slowing it down
A fuller world that still runs smoothly.
- Checking access
Lesson 29: Bring it to life: grass and characters
Life on the ground, and characters that hold together when they move.
The water0 / 2
- Checking access
Lesson 30: When the AI suggests the wrong tool
The AI suggested a paid 3D tool. Jeff thought the reference didn't use it, and he was right.
- Checking access
Lesson 31: Build what's under the water
Build the seabed, then let the water show it.
Ship it0 / 3
- Checking access
Lesson 32: Test it like a player
Prove the game works the way a person plays it.
- Checking access
Lesson 33: Put it online with Vercel, step by step
A link you can share, with only the files the game needs.
- Checking access
Lesson 34: Share it, and pick your next step
An honest list of what one afternoon didn't cover, and what to do next.
Bonus: turn your build into content0 / 3
- Checking access
Lesson 35: Reels from your build
Short clips from real gameplay, made the day after.
- Checking access
Lesson 36: Music and sound effects
Give your clip sound that matches the game.
- Checking access
Lesson 37: Cloning your voice for narration
Narrate in your own voice without recording every line.
Included with the course
Open up the project.
The source download lets you look past the lesson: read the structure, follow the logic and get the project running on your own machine.
- tidelight/
- The code behind the build
- Resources
- Project resources and build notes
- Source vault
- Download after a fresh access check
Downloads come from the Source vault while you’re signed in. No GitHub account needed. Release version and contents are listed there when a release is published.
Meet the maker
Built and broken down by Jeffrey Oyeneye.
A video producer bringing the same attention to story, rhythm and detail to games, websites, and the process of teaching them.
Before you begin
A few good questions.
What do I get with a free account?
Chapter 1 of every course and the community. Start with the direction, then decide which full project you want to explore.
What does $29 per course include?
A one-time purchase includes every chapter of the course and the project’s source code, with its resources and build notes. It stays in your library.
Do I need to know how to code?
The breakdown explains the creative decisions and the agent workflow as it goes. Any setup the source needs is listed with its release.
Are the lessons recorded?
Recordings are being published course by course. Each chapter says whether its video is out yet, and the outline is open to read now.
What is the refund policy?
The refund policy is pending Jeffrey’s approval. Final terms are shown before checkout.