Opus Lab is a community for founders, operators and creators who build with AI instead of talking about it. I do not think AI education should sit behind a paywall, which is why I made this and why it is free. Everything I learn lands here first, usually before it is tidy enough to publish, and we get on a live call every week.
Post what you are working on, get it taken apart, and watch other people do the same. We get on a live call every week, and builds get walked through end to end, including the parts that did not work. Everything published to date is included the day you join.
Every build gets drawn out: what calls what, where it breaks, what it costs to run. You leave knowing why it works, which is the only way to change it later when it stops.
Each one ends with something running on your own machine, not a certificate. No code needed to start any of them, and a live call every week to bring what you are stuck on.
A trusted system outside your head. CODE and PARA running, a fifteen minute weekly review, and a path from random notes to finished work.
Plug Claude into Drive, Gmail and Calendar so it works on your real information. One connector live by the end, and a handful of prompts you actually use.
The three acronyms in every AI tutorial, explained so you can open a terminal without fear and know what each one is for.
Write the AGENT.md that reliably steers an agent: tools, permissions, and a debugging loop for the day it misbehaves.
Package your know-how into a SKILL.md the AI loads on demand, so your brand voice and your report format stop being a paragraph you retype.
For founders, operators and creators who are past the tutorial stage and into the part where it has to survive real users.
| What it is not | What it is |
|---|---|
| A signals group. | Builds, posted and taken apart in the open. |
| A prompt dump. | Prompts, skills and playbooks that shipped on real work first. |
| Talking about AI in the abstract. | A live call every week, about what you are actually stuck on. |
| A certificate. | Five lessons that end with something running on your machine. |
| Watching from the feed. | People with a business or a body of work to point this at. |
No. Every lesson starts in plain English and needs nothing but the tools you already have. If you can follow a recipe, you can follow these. You will be more dangerous if you can code, but it is not the entry ticket.
Start in the classroom with the lesson closest to your problem, then post what you are building in the feed. The live call is on the calendar every week. The fastest way to get value is to bring a real thing you are stuck on.
Same material, run in a room instead of against your own workflow. If you want it built into your business with a handover, bring me in. Plenty of people start in the Lab and do that later.
On Skool, at skool.com/opus-lab-4972. Skool runs the room; I run what goes in it. Works on the web and in the Skool app.