::path · builder · free · cc-by 4.0
Builder · ship something real
You want to make something. Side project, business, app, art piece. The path here gets you from idea to shipped in ~6 weeks.
::fit for
- ·Anyone with a half-built side project gathering dust
- ·Anyone who has tried to learn to code for the third time
- ·Anyone who has an idea they keep mentioning at dinner
::NOT for
- ·Anyone who needs to keep their day job stable first — Worker path
- ·Anyone who already runs something — Operator path
::the ordered path · do them in order
Week by week.
Roughly 3 lessons per week is the honest pace for an adult with a job. Faster possible. Slower also fine. The order matters more than the speed.
::week 01
I'm scared of AI · the calm starting point
Before any lesson, the feeling. Whether you are scared, skeptical, exhausted by the hype, or quietly excited and hiding it — this is the door. None of the feelings are wrong. The path is yours.
What AI actually does — autocomplete at huge scale
Strip the magic feeling off. Get the working model of what AI is doing under the hood, so the rest of the curriculum has a foundation.
Your first real prompt — be specific, not polite
Stop typing into AI like you're texting a friend. The prompt is the entire skill at this level.
::week 02
System prompts — telling AI who to be
Every AI conversation has a hidden first instruction. Knowing how to set yours is the difference between a generic answer and one calibrated to you.
Refine, don't restart — the second draft is where it lands
The biggest skill jump at this level: stop deleting the conversation and starting over when an answer is wrong. Refine in-place.
When AI gets it wrong — see a hallucination, on purpose
You will not respect the verify rule until you watch AI lie to your face with full confidence. Do it now, on a low-stakes question, where the cost is zero.
::week 03
The verify rule — three categories of trust
Not everything AI says needs verification. Most things don't. Knowing which third does is the skill.
Few-shot — teach by example
Three good examples will outperform a one-paragraph instruction every time. The skill is curating the examples.
Multi-turn conversations — letting the chat build a model of the task
At User level, a single prompt is rarely the win. A 5–10 turn conversation that builds a working model of your task is.
::week 04
Documents in chat — when paste vs. upload matters
AI is at its best when reading something specific. Knowing how to feed it documents is the next leverage step.
Image-in-chat — paste the screenshot
Most people describe what they see when they could just paste the screenshot. The AI reads pixels better than you can describe them. Stop typing the picture.
Voice mode — when speaking beats typing
Real-time conversation with AI is a different shape than chat. Knowing when to switch modes is the actual skill.
::week 05
Projects and Custom GPTs — stop re-explaining yourself
Every chat starts cold. A Project remembers your background, your style, your files. Create one for the work you actually do every week, and stop pasting the same context twelve times a day.
Artifacts and Canvas — the side panel that runs your work
Claude Artifacts and ChatGPT Canvas turned chat into a workspace. Code runs. Documents render. Edits happen in place. This is where AI stops being chat and starts being a tool.
Model routing — switching between Claude, GPT, Gemini mid-task
Operators don't pick one AI. They route each task to the model that does it best. Knowing the strengths is the skill.
::week 06
MCP servers — the plug socket that turned AI into a real tool
Model Context Protocol is the standard plug. Knowing what plugs in changes what your AI can actually touch — your files, your inbox, your calendar, your repos.
Agent mode — when AI takes action, not just answers
The frontier of useful AI is agents that DO things — browse, click, file, send. The actual skill is the safety pattern, not the magic.
Computer use — when AI takes the mouse and keyboard
Claude in Chrome, ChatGPT Atlas, computer-use beta — the frontier is AI that drives your browser like a human. Knowing the safety pattern is the actual skill.
::week 07
Your first paid tier — which one, when, why
Free tier is enough for most humans for 30+ days. When you outgrow it, you pay for ONE tool. Not four.
The senior-engineer pattern — talk to AI like a senior
A junior asks for the answer. A senior asks for tradeoffs, edge cases, alternatives, and reasons not to do the thing. Run that same five-step pattern through any AI conversation and the output roughly doubles in quality.
Outgrowing the chat box — when chat isn't the right surface anymore
At Pilot level the chat box is a tool, not the system. You need persistent project memory, multi-tool routing, and receipts on disk. This is the bridge to a cockpit.
::part of the AtomEons /learn curriculum · 5 paths · cc-by 4.0