No buffet. No "explore at your own pace." Follow these four steps in order and you'll have shipped your first AI build by the end of the day. Skip ahead at your own risk — each step sets up the next.
Two are written end-to-end below. Two more are queued — outlines visible so you know what's coming.
The four pillars (weekly build guides · resources · tools · community mentoring), how membership works, what to expect in your first week. If you came expecting a content library or a Discord hangout, this is where you find out you're in the wrong place.
Install Claude Code, configure your ~/.claude/CLAUDE.md, add the AOF skills bundle, and verify /init works. Other tools (Cursor, v0) are fine — but every weekly guide assumes you have Claude Code working as a baseline.
A 5-question intake (need-planning tool) that turns a vague AI idea into a scoped, shippable build. By the end of step 3, you'll have a specific build picked, the right weekly guide queued, and a ship-by date on the calendar.
After completing the build, drop a short post in the community thread for week N: what you built, what broke, what you'd do differently. This is how community mentoring works — your wins become tomorrow's tutorials, your stuck moments become someone else's "I had that exact problem."
Three things you can do right now — even before Step 01 — that compound for the rest of your time here.
Pin /community/ to your bookmarks bar. You'll be back here weekly.
One-page reference for slash commands, hooks, MCP. Tape it to your monitor. Open →
Get a feel for which tool to use for what. You don't need to memorize it — just know where to look. Open →