Burn less · Techniques pack
You've used over 75% of your weekly usage limit.
When the usage warning hits, treat it as a systems problem — one job, anti-jobs, dogfood, approval gates, fleet shape.
Draft — not posted yet X thread coming — not published until Buzz OK.
Technique
- One job + explicit anti-jobs (Eggbot bar).
- Skills + memory + routines over mega-prompts.
- Dogfood before “ready”; approval before send.
- Coordinator + specialists; scope cuts; clickable paths.
Related stubs: one-job · anti-jobs · dogfood · skills-routines · approval-gates · fleet-ops · clickable-paths
Draft X thread (1/6–6/6)
Target ~270–280 classic X chars each. If @BuildBotsBetter is on X Premium, we can go long-form later.
Draft — not posted yet 1/6 · ~282
You've used over 75% of your weekly usage limit.
That warning isn't failure — it's feedback. You're paying for retries on mushy bots.
Build Bots Better fix from Galaxy: cut waste without killing speed. Steal these five moves.
Messy design burns quota.
Thread ↓ · @BuildBotsBetter
Draft — not posted yet 2/6 · ~278
1) One job. One voice. Explicit anti-jobs.
Most token burn is a bot wearing five hats. Write the job in ONE sentence. Next: what it must never do (no send without approval, no inventing metrics, no "ready" without dogfood).
Job needs an "and"? Split it. Eggbot bar — steal it.
Draft — not posted yet 3/6 · ~273
2) Skills + memory + routines beat mega-prompts.
Mega-prompts rot every model swap. Saved learnings compound.
Map work into skills (1–2h). Put repeats on a routine. Ask: "Read my past Slack and write a style guide."
Silence is a feature — ping only when something moved.
Draft — not posted yet 4/6 · ~278
3) Dogfood before "ready." Approval before send.
"Ready" isn't a vibe — it's a pass you ran yourself. Click the path. Read the draft. Break the happy path.
Outbound: research + draft freely. Send only with a human gate. Keep provisional work provisional until that gate lands.
Draft — not posted yet 5/6 · ~275
4) Coordinator + specialists. Scope cuts. Clickable paths.
One conductor. Many one-job players. Ship the night-of console; cut extras until you need them.
Never hand a bare site/foo.jpg — use https, file://, or attach the file. Broken handoffs mean more chat and more burn.
Draft — not posted yet 6/6 · ~274
5) Usage drops when the system is clear.
Fewer re-prompts. Fewer "which bot?" loops. Fewer redo regenerates. Clear jobs burn less than messy fleets.
Checklist: https://buildbotsbetter.com/resources/usage-75/
More: https://buildbotsbetter.com/resources.html
Teach the fleet once — stop re-prompting.
@BuildBotsBetter