Keep climbing—one practice at a time.

Path to Mastery

A simple practice ladder so skills stick after you finish the main path.

After you ship a walkthrough; Intermediate recommended first
Person building at dual monitors
Mastery is practice with feedback—not reading alone.

What “mastery” means here

Not memorizing every flag. You can take a messy idea, use Grok safely, check the result, and finish a small slice without getting lost.

Level 1

Operator

Install, sign in, attach files with @, approve tools carefully, write goals with a check step, cancel with Esc, resume sessions.

Level 2

Director

AGENTS.md, plan mode, compact/fork, strong prompts, sensible permission modes, skills for repeated work.

Level 3

Systems builder

MCP, hooks, headless scripts, workflows/goals, multi-session work, game asset pipelines.

Weekly practice (simple)

  • Day A: One tiny logic change + write how you verified it.
  • Day B: One UI or “feel” improvement you can see.
  • Day C: One plan-mode design for something slightly hard—build only if the plan is good.
  • Friday: Save one good prompt into a skill or a NOTES.md snippet.

Self-check list

  • □ I can install and open Grok without help
  • □ I know history (above) vs typing box (below)
  • □ I use @ when I know the file
  • □ Every serious prompt includes how I will verify
  • □ I stay on Ask mode until I trust the project
  • □ My project has AGENTS.md
  • □ I can compact or start a new session when the chat feels messy
  • □ I finished at least one full game or app ship
Final exam (90 minutes)

Pick one: (A) Re-run the First Game or First App walkthrough without skipping Done when checks, or (B) invent a tiny project with AGENTS.md + a one-page slice/journey, ship it, rename the session, and write three bullets on what you would improve next. Do not do both at once.

Keep the Master Cheatsheet open for two weeks. Use the Glossary when a word confuses you.