Grok School
Map of Grok
M01 · 7 min

When to use what

A decision tree so you stop using chat for everything.

Weak
Strong
Paste whole codebase into chat and hope
CLI in the repo, or @file references, or Build web for greenfield
Ask Build web to “make a bank app” with no constraints
One user, one flow, one definition of done, mobile-first
Let the agent rewrite 40 files unsupervised
Plan mode → approve steps → review diffs → run tests
Use Imagine as the product (pretty screenshots only)
Ship working UI; Imagine for hero/empty states/textures
  1. 01

    Greenfield demo or consumer app

    Start in Grok Build web. One sharp prompt. Publish. Iterate in chat turns.

  2. 02

    Existing repo / production code

    Grok Build CLI in the project root. Plan mode for multi-file. Headless for CI-like chores.

  3. 03

    Product feature inside your backend

    API with grok-4.5 (or Responses/agent paths). Structured outputs + your tools.

  4. 04

    Research + strategy

    Chat with search. Then distill a Build brief — don’t stay in chat forever.

Next