Grokbot TemplatesGrokbot Templates
Todos los casos de uso

Trabajo

Build ships the app; Bot runs the company

One chat for code, inbox, stills, and publishing burns tokens and ships half a company.

Compartir

Qué dolía

Arian (@arianlooterking) used to treat Grok Build and Grok Bot as synonyms — one agent for everything. He now splits surfaces: Build is the terminal coding agent on the repo (plan mode, diffs, /skillify); Bot is always-on teammates with their own computer for inbox, research, stills, publishing. One outcome per surface; no second coding loop in Bot on the same repo.

Qué instalar o crear

1) Build ships the app — plan mode on messy work, approve plan, review diffs, /skillify sharp sessions. 2) Bot runs the company — named seats, chief of staff routes, specialists own one lane. 3) PR → Build; draft/routine/handoff → Bot. 4) Don't reopen the same repo in Bot just to help. 5) Drafts first, autonomy second.

Bots

  • Chief of staff

    Route work to specialist Bot seats. No mega-bot coding.

  • Specialists

    One lane each: inbox, research, stills, publishing.

Plugins

  • Ninguno el primer día. Sigue los pasos del primer uso.

Rutinas

  • Show a Bot the workflow once, then let the routine run; expand leash after the seat is sharp.

El prompt

Esto es un consejo, no un prompt de sistema para pegar. El autor no publicó uno. Sigue los pasos del primer uso.

Primer uso

  1. 1Read the full note in https://x.com/arianlooterking/status/2097854884292804875.
  2. 2Install/open Grok Build for repo work; keep plan mode on ambiguous edits.
  3. 3Keep Grok Bot for inbox/research/design/publishing with named seats + a router.
  4. 4Rule: next move is a PR → Build. Next move is a draft/routine/handoff → Bot.
  5. 5Refuse one mega-bot that codes and also manages the company.

Valla de aprobación

Build plan mode blocks edits until you approve. Bot: drafts before autonomy; you approve send/spend/publish.

Qué ajustar

Steal the surface rule: coding stays in Build; company ops stay in Bot. Mixing both in one thread is how context dies.

Fuente

Arian @arianlooterking · Publicación original

Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.

Explorar plantillas

Explorar planos de equipo

Paquete Pro

¿Quieres la configuración completa, no solo la idea?

Los paquetes Pro te dan el texto de la tarea, los prompts, los horarios y los tropiezos de los casos de uso más populares.

Ver Pro