Engineering
Four-bot site build: turn every bug into a rule or a test
Weekend builds ship bugs that die as chat comments instead of lasting gates.
What hurt
intelligence (@martin_ict_algo) shipped a kana/kanji learning site with four Grok Bot agents: brief → design picks → content before code → product pass/fail → Cursor cloud PRs with tests → review loop (max 3) then human merge. Lesson: when you find a bug, turn it into a rule or a test, not a review comment. Not affiliated with xAI.
What to install or create
Role-split bots → content before code → PASS/FAIL gates → bug → rule/test.
Bots
Brief / Design / Content / Product
Split weekend ship roles; human is the merge gate.
Plugins
GitHub
Required
Browser
Optional
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/martin_ict_algo/status/2111941656127909989 (credit @martin_ict_algo).
- 2Write a one-page brief (tone, learning order, non-goals) before any UI code.
- 3Ask design for 2–3 live directions; pick one consciously.
- 4Freeze content as plain lines before coding; lock product rules as pass/fail checks.
- 5On every bug: add a rule or automated test, re-run, then you merge—max a few review passes.
Approval fence
Nothing merges without your yes after the review loop.
What to tweak
Steal the close: every catch becomes a rule or CI check before the next pass.
Source
intelligence 🇦🇺 @martin_ict_algo · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.