Learn Grok Bot — Development skill for Claude Code

[English](./README.md) | [中文](./README.zh.md)

Learn Grok Bot — An AI Employee With Its Own Computer

Grok Bot is not a chatbot. It is not a coding CLI with a window.

It is a **desktop AI employee**: a named persona, a Linux computer of its own, and one voice (`SendMessage`). Who wakes it changes the rules. Dangerous work goes through a gate, then a human.


Each lesson does two jobs: **name the product object**, then **show how the reconstructed tree enforces it**. Objects without code are a story. Processes without objects are a roster.

• PRODUCT.md — five objects, the wake table, one full task
• ARCHITECTURE.md — product graph + runtime graph + product verbs = which RPC table

---

The mindshift

A terminal coding agent owns your repo. A Grok Bot employee owns **another computer**.

The polished UI is the least trusted process in the building. It paints `SendMessage` as bubbles. It must never run a shell, read a secret store, or leak the model's inner monologue into the chat.

Product fact	If you invert it
The user hired a roster employee	You shipped a completion
Plain model text is invisible	Drafts and tool plans flash in the chat
"My computer" is the shared box	rm runs at home
A [routine] may stay silent	Cron spam: "(no change.)"
A widget ends the turn	The employee keeps talking while waiting

Renderer / preload / main / coordinator / host / box are load-bearing walls. The walls are not the product.

---

16 lessons, by object

**Each lesson = product invariant + implementation dissection + runnable teaching code.** The motto is a reminder. The body must say which process owns the object, and whether prompt, middleware, or a hard gate nails the invariant.

Stage 1 · Product objects

**s01**   *"You hire an employee, not a completion"* — roster, persona, `[first run]`

**s02**   *"Plain text is a monologue; SendMessage is