Engineering
Write your team's tribal knowledge into a repo of Markdown files, then let routines check work against it
Naming conventions and ticket formats live in people's heads, so every review repeats the same notes.
What hurt
Yoyo Besser (@yoyo_besser) and his team spent a week writing a git repo of Markdown files covering everything from naming conventions to Jira ticket formats and calendar invite content. Not affiliated with xAI.
What to install or create
Grok Bot routines now verify that everyone's work matches those standards, which acts as a guardrail without anyone policing it by hand.
Bots
No new bot. Follow the first-run steps.
Plugins
GitHub
Required
Routines
Standards check. Daily or on new work. Compare new tickets, names and invites against the standards repo and list mismatches.
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/yoyo_besser/status/2108981326984384811 (credit @yoyo_besser).
- 2Start a repo with one Markdown file per standard (naming, tickets, invites).
- 3Point a routine at it and at the work to check.
- 4Have it post a short list of mismatches with the rule each one breaks.
Approval fence
Routines report mismatches; people fix them.
What to tweak
Standards the bot can read become standards the bot can check.
Source
Yoyo Besser @yoyo_besser · 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.