20 Grok Bot prompts distilled from Lauren Tan's public pstack

kocer @kocer_ethOriginally posted 2026.09.22

Open original on X

PART 2: I FOUND 20 MORE PROMPTS IN LAUREN TAN'S PUBLIC PSTACK. USE THEM IN GROK BOT WHEN "BUILD THIS" STOPS WORKING. part 1 gave you 50 prompts pulled from the public xAI company build. for part 2, I went through Lauren Tan's public pstack, which is available inside her Grok Bot. I converted 20 real playbooks into paste-ready commands for when a build starts touching production. 1. find the failure › 01. reproduce [bug]. find the root cause, fix it, and prove it at runtime. › 02. profile [slow flow]. show the baseline, identify the bottleneck, and measure the result after the fix. › 03. diagnose [live symptom] from instrumentation. do not guess from the source code alone. › 04. inspect [trace]. rank the likely causes and verify the dominant one in the running product. 2. settle the design › 05. /architect settle the caller, types, data shape, and module boundary before writing code. › 06. /blast-radius trace every caller this change could break. prove the condition that makes it safe. › 07. build two throwaway prototypes. assign one agent to each and compare them side by side. › 08. /arena run my request unchanged across multiple models. combine only the strongest parts of each proposal. 3. build against reality › 09. build [feature] behind a feature flag. verify the user-visible behavior inside the real app. › 10. compare [reference screenshot] with [current screenshot]. reproduce the mismatch and iterate until they match. › 11. /tdd reproduce this bug with a failing test first. implement the smallest fix and rerun the test. › 12. migrate every caller to [new API]. preserve existing behavior and delete the legacy path. 4. attack the work › 13. /swarm give one package to each worker. run its check script and return one consolidated report. › 14. /interrogate review this PR. ask several models to find correctness, design, and code-quality failures. › 15. /show-me-your-work keep a reviewable trail of decisions, rejected alternatives, and evidence used. › 16. split [migration] into verifiable phases. make sure every phase ends in a shippable state. 5. finish without babysitting › 17. watch PR 123 until it is merge-ready. resolve conflicts, review threads, and CI failures. › 18. verify every PR independently. report exactly what prevented any PR from merging. › 19. /reflect capture why this task took too long. turn the lesson into a reusable skill or automated check. › 20. /automate-me study my recent workflows and draft a personal mode that routes through pstack. with these prompts, Grok Bot stops being a code generator and becomes an engineering workflow you can inspect. bookmark part 2 for the first task that survives the demo but fails in production.

This post quotes another post: x.com/kocer_eth/status/2092216029816472002