Session #1:

The Creator  Training Opening

30 minutes | Context-Driven Development

The Promise

By 5pm today, you will:

  • Build and deploy a live 4-player multiplayer game
  • Learn to architect context instead of writing code
  • Become a Creator: one person doing the work of PM + Designer + Developer

Traditional way: 4 people, 3 days
Today: You, 6 hours

Demo: What You're Building

[LIVE: Play 4-player Simon on phones]

  • No login, just click a WhatsApp link
  • Real-time multiplayer sync
  • Works perfectly on mobile
  • Deployed and live on the internet

[SHOW: GitHub repo with .cursorrules folder]

  • 12 context files = 120KB of specifications
  • AI wrote the code by following these rules
  • 6 hours instead of 3 days

Working in Human Language

You won't need to memorize commands or syntax.

Traditional Way:

git checkout -b feature/lobby
git add .
git commit -m "Add lobby component"
git push origin feature/lobby

Your Way Today:

Just talk to Cursor:

  • "Create a new branch for the lobby feature"
  • "Commit these changes"
  • "Deploy the frontend to Render"
  • "Make a pull request"

You speak. Cursor translates. Tools execute.

The tools we're using:

  • Git (version control)
  • Cursor (AI-powered editor)
  • Render (deployment)
  • MCP (connects them all)

The Old Way: Code-First

Brain → Keyboard → Code → Debug → More Code → More Debug → Ship

Problems:

  • Amnesia: forgot why you made decisions
  • Lost intelligence: requirements in ignored docs
  • Handoff hell: context dies between people

Your intelligence lives in your head. Heads are terrible hard drives.

The New Way: Context-Driven Development (CDD)

Brain → Context Files → AI Reads Rules → AI Writes Code → Ship

The Shift:

  • Persistent memory: rules never forget
  • Crystallized intelligence: decisions become executable specs
  • One owner: you define everything, AI executes

You write the brain. AI acts as the hands.

The Three Pillars of Context

1. Product Context (The "Why")

.cursorrules-product

  • User journeys, friction points, success metrics
  • Example: "No passwords. Players join via WhatsApp link"

2. Design Context (The "Look")

.cursorrules-mobile-ui

  • Pre-calculated constraints, responsive math
  • Example: "iPhone SE = 375px. Four buttons = 170px each"
  • AI doesn't guess. It follows your math.

The Three Pillars of Context  

3. Technical Context (The "How")

.cursorrules-tdd, .cursorrules-architecture

  • Architecture decisions, quality gates, workflows
  • Example: "Write failing test before any code"
  • AI refuses to write code without tests

Today's Journey

Morning (9:00-12:30): Build the Brain

  • Product Manager: Define requirements
  • Designer: Solve mobile math
  • Architect: Create context files
  • No code yet

Afternoon (13:30-17:00): Direct the Execution

  • Builder: Use pointer prompts
  • AI follows your context
  • 5-15 min per feature (vs 30-60 min traditional)
  • Deploy and play on real phones

You Are Now a Creator

Not a developer. Not a PM. Not a designer.

A Creator - someone who architects context and directs AI execution.

Questions?