Engineering
Five bullets before Composer: goal, files, out of scope, kill switch, review
Long chat retries burn tokens; a short plan before Composer cuts rework.
What hurt
Caribedevs (@cristianmock) shares a concrete weekly tip with Cursor + Grok Bot: before opening the composer, write five bullets — objetivo (goal), archivos (files), out of scope, kill switch, review. That short plan saved two retries and cut tokens ~30% on a Shopify fix. Plan corto > chat largo. Tip only. Not affiliated with xAI.
What to install or create
Five bullets first → then Composer → kill switch ready → review after.
Bots
Pre-composer plan bot
Refuse to open Composer until five bullets exist; keep kill switch and out-of-scope visible.
Plugins
None on day one. Follow the first-run steps.
Files
Sticky note or chat pin: goal / files / out of scope / kill switch / review.
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/cristianmock/status/2103982802761068546 for the five-bullet tip.
- 2Before opening Composer (Cursor or Grok Bot), write: goal, files, out of scope, kill switch, review.
- 3Keep out of scope and kill switch on screen while the agent edits.
- 4Run the fix; if it wanders, hit kill switch and restate the five bullets.
- 5After: one-line review — what worked, what burned tokens — before the next composer session.
Approval fence
Kill switch and out-of-scope stay explicit so Composer cannot wander into deploys or secrets.
What to tweak
Steal “plan corto > chat largo.” Goal / files / out of scope / kill switch / review before you type.
Source
Caribedevs @cristianmock · 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.