Your first thirty days

It is an online school for building AI automation systems you own. The teaching happens in live follow-along classes: a command is typed on screen, you type it too, and when it breaks the fix is part of the lesson. Recordings and write-ups are mirrored into the Classroom Library every day.

Around the classes sit courses on Claude Code, n8n and AntiGravity, a self-hosted n8n workflow library, a prompt library, and Build Packs — ordered prompt sets that install a whole system on a clean machine. The school is run by Hector Diaz, who has thirty years in software and runs Orbix Automation Solutions in Pennsylvania.

One course, one Build Pack, one real process of your own. In that order. The most common way to waste the first month is to start four things.

1. 1Week 1

   Set up the machine and finish one course

   Nothing else works until you have a box you control. Pick one course — the Claude Code Tutorial or the AntiGravity Course — and finish it end to end rather than sampling three.

   • Install Docker, PostgreSQL and n8n on a machine or VPS you own.
   • Install Claude Code and sign in.
   • Finish one course start to finish. Do not start a second one.
   • Bring whatever broke to the live class.
2. 2Week 2

   Run one Build Pack all the way through

   A Build Pack is an ordered set of prompts you paste into Claude Code one at a time. Run one to the end, on your own box, against your own keys. At the end you have a working system rather than notes about one.

   • Pick a pack whose subject you actually understand.
   • Read its "what was verified and what was not" section before you start.
   • Paste the prompts in order. Do not skip ahead.
   • When a prompt produces something wrong, fix it and keep going — that is the exercise.
3. 3Weeks 3 and 4

   Rebuild one real process of your own

   Take one process from your work or your home that you already do by hand, and rebuild it with what you now have. Not a demo, not a tutorial project — something whose output you will actually look at next week.

   • Write down the process as it happens today, step by step, before automating anything.
   • Automate the boring middle first, and leave the judgment calls to a person.
   • Run it for a week before you touch it again.
   • Post what broke in the community. That write-up is worth more than the workflow.

Four things, on a machine or VPS you control. Not on someone else's platform — the whole point is that when you stop paying anybody, it keeps running.

• Docker

  Everything else runs inside it.

• PostgreSQL

  The one place your systems keep state.

• n8n

  Where workflows live. Self-hosted, on your machine.

• Claude Code

  The terminal agent that writes and wires the rest.

The Claude Code Tutorial course walks through the install on Windows with WSL2, macOS on Apple Silicon, and Linux. If your machine fights you, that is what the live class is for.

No, but you need to be willing to use a terminal. Most of what you will do is describe what you want in plain language, watch an agent write it, then read what it wrote closely enough to catch it being wrong. That last part is the actual skill.

There is no track here that avoids the command line. If that is a hard no for you, this is not the right school and it is better to know that on day one.

Membership is $20 a month, $50 a year, or $99 once for lifetime access. The full table of what each tier includes is in the pricing section of the home page.

The free Skool community is a separate thing at a separate price. You do not need it to use the site, and the site membership does not include the paid Skool group.

Questions before you join? Email [email protected]. A person answers.