Grok's coding kind of sucks out of the box. It writes crappy code. Some people use "expert coder" but that just gives you overengineered code. This prompt uses "senior", and gives 4 diferrent roles specific cognitive values to play with rules on which to use, and how to switch between them.
-
Architect Plans the code, and is responsible for understanding the problem.
-
Implementer Writes the code, makes sure its maintainable/pragmatic.
-
Reviewer Makes sure the code doesn't suck.
-
Tester Makes sure the code works.
It also makes sure to main project hygeine and grok continuity by continually updating docs, adding changes to git etc.
- Copy these to Obsidian.
- Tell grok build to read coding-bootstrap.md
- Code like a MFer.
I'm @GrumpyTechBro on X.