McVay AI Classroom
The Field Guide gets people their first win. The Classroom turns that first prompt into a repeatable workflow with a simple weekly rhythm, a private-room feel, and clear help when beginners get stuck. Bring the messy task, get the plain next move, save the workflow, and check it before trusting it.
Classroom library
The Classroom should feel easy to enter: watch the next short lesson, post the messy question, save the workflow card, and check the answer before trusting it.
For the person staring at the blank box.
Watch next
For the beginner who opens ChatGPT and does not know what to type. The lesson gives one job, one prompt shape, one answer format, and one proof check.
Bring the messy task and the rough output.
Watch one short step, then take one action.
Know which proof step is finished.
Only after one business workflow works.
Plain English before the first account.
Browser, mobile app, account, free vs paid.
Give it one real job and one answer shape.
Make the rough answer sound useful.
Free guide to Classroom
The public guide gets people moving. The Classroom is the guided layer for turning the first prompt into one saved workflow and one repeatable AI habit.
Classroom rule
The Classroom can borrow the proven community shape, but the job stays plain: help people ask one useful question, save one workflow, and prove the output before they use it.
Members should leave the sprint with one repeatable AI workflow, not a pile of half-watched lessons.
The preview teaches messy beginner questions, plain fixes, prompt cleanup, and weekly proof.
The join button stays internal and placeholder-only until the actual Classroom is ready.
Member workbook
Each week should produce a small artifact a beginner can reuse: prompt, workflow card, workspace rules, proof check, and one simple win post.
One task, the context AI needs, the output shape, and the tone.
What was wrong with the first answer and the follow-up that improved it.
The repeatable recipe so next week starts faster than today.
What must be checked before the answer touches real work.
Classroom portal preview
A beginner should not have to invent a perfect post or understand every AI tool before getting help. The room starts with one real job, one plain question, one reusable workflow card, and one proof pass before the answer gets used.
Give people copy-ready language for "what should I type?" instead of a blank composer.
Task, inputs, prompt shape, output format, review checklist, and when to reuse it.
Paste the prompt, the rough answer, and what you wanted instead. Then fix one step.
Names, numbers, dates, privacy, promises, tone, and next action get checked before use.
What the Classroom is selling
The Field Guide can teach the first move by itself. The Classroom exists for the follow-through: posting the messy task, getting the prompt cleaned up, saving the workflow card, and proving the result before it touches real work.
Start Here posts, prompt repair, workflow questions, business examples, and useful wins.
One lesson, one action, one saved workflow card, and one proof check each week.
Planned lesson drop, working room, office-hour style review, and Friday proof post.
Roles, local profile, learner lane, workflow builder lane, and real member proof later.
30-Day Sprint Map
This is the guided path. It avoids the giant course-vault problem and gives beginners one clear result to chase: Start Here, Prompt, Workflow, Workspace, then Proof.
Choose one task, one lane, and one thing not to paste into AI.
Move from blank box to one useful answer saved.
Turn the useful answer into a reusable workflow card.
Create one workspace plan with context, rules, and boundaries.
Check facts, privacy, tone, numbers, names, promises, and the next action before using it.
Classroom rooms
This borrows the proven community/classroom shape without copying another brand or pretending the room is already full.
Welcome, how the sprint works, choose your starting lane, and what not to paste into AI.
Member action: My first AI job is ___.The Blank Box Problem, Task + Context + Format, first answer as draft, and what to save.
Assignment: run, revise, and save one prompt.First answer vs repeatable workflow, bad-output recovery, and the workflow card.
Assignment: fill out one reusable workflow card.Random chat vs workspace, Claude Workbench basics, one job, and one rules sheet.
Assignment: draft one workspace plan.Check names, numbers, dates, privacy, tone, promises, and next action before using the output.
Assignment: post one verified result and the checks you ran.Prompt shelf, workflow cards, safety checklist, Claude Workbench template, and Codex rules sheet.
State: resource library shell only.Saved prompt, workflow card, checklist, draft, or verified customer-safe reply after real members exist.
State: empty until real proof exists.Weekly lesson drop, one live working session, one office-hour block, and catch-up time.
State: no fake dates or fake events.Profiles, lanes, and progress tags later when the Classroom is real.
State: no fake online status or member count.Weekly rhythm
A beginner does not need ten calls and a vault of unfinished lessons. They need a weekly move, a place to ask for help, and a small proof post at the end of the week.
One short lesson and one exact action.
Members share the task they want AI to make easier.
Prompt clinic or live working room. Planned, not yet live.
One review block or async review. Keep the load sane.
What did you make, save, or verify this week?
No-pressure review, save the workflow, and reset for Monday.
First post kit
The community should give people the words. The first post is not a status update. It is a practical request: here is the task, here is the messy context, here is what a good answer should look like.
"I want AI to help me with one real task. Here are my notes. A good answer would be a reply, checklist, plan, summary, or script."
"Here is the prompt. Here is the rough answer. The problem is tone, length, missing steps, vague wording, or wrong format."
"I used AI to make this. I checked names, numbers, dates, privacy, tone, promises, and the next action before using it."
Resources and progress
These are structural previews. The copy stays honest until Chance opens the actual join path and real members start posting.
Task, inputs, prompt shape, review checklist, final format, save location, and when to reuse.
Workspace name, job, files or notes it needs, instructions, things to avoid, and expected proof.
New, First Prompt, Workflow Built, Workspace Drafted, Proof Posted, Ready For Next Sprint.
Open members and progressMy first AI job, fix my bad answer, and weekly win prompts so beginners know how to ask.
Maximum one live working session and one office-hour block per week.
Customer replies, content, admin cleanup, SOPs, and future Boardroom implementation.
Proof board
This board is an honest empty state. It shows what a real member win must include after the Classroom opens.
The member can show what they typed and what answer was worth saving.
Preview stateTask, inputs, prompt shape, output format, and review checklist are written down.
Preview stateRules, files, examples, boundaries, and proof step are ready for reuse.
Preview stateNames, numbers, dates, privacy, tone, promises, and next action are reviewed.
Preview stateThe member knows what repeatable task to improve after this first workflow.
No fake member proofJoin Classroom
The safe launch path is preview first, join link coming soon after Chance approves the mechanism, then beta cohort, then founding classroom. This page is the local preview of what buyers will see.
Start with the Field Guide and get one useful AI answer.
Pick one repeat job that would be worth saving as a workflow.
Use the Classroom preview to see how the guided sprint works.
Start with the Field Guide, preview the local Classroom room, and keep Boardroom in the future lane until the core sprint is ready.