كل حالات الاستخدام

الهندسة

Paste one prompt: lead bot + security, performance, and QA

You become the middleman forwarding every message between specialist bots.

مشاركة

نقطة الألم

@Solomonrojie publishes a stealable setup: one lead owns the plan and final package; security, performance, and QA investigate in parallel with file ownership, compact handoffs, and a hard stop after two failures. Paste the author prompt; require your OK before merge/deploy. Not affiliated with xAI.

ماذا تثبّت أو تنشئ

Paste setup prompt → review proposed config → run investigations → you approve merge/deploy.

الروبوتات

  • Lead + 3 specialists

    Lead owns plan/review; security, performance, and QA investigate in parallel.

الإضافات

  • لا شيء في اليوم الأول. اتبع خطوات التشغيل الأول.

الروتينات

  • لا شيء في التشغيل الأول. راقب تنفيذًا يدويًا واحدًا أولًا.

النص التوجيهي

Lead + security/performance/QA setup (author-quoted)

Quoted from @Solomonrojie — as published. Do not invent a second system prompt.

السطر الأخير هو حاجز الموافقة الذي أضفناه: Never send, post, spend, or buy without my explicit yes.

Build my engineering workflow around one lead Bot and three specialists: security, performance, and QA.

First inspect the repository, available tools, and existing test commands. Report missing access.

Create the Bots with distinct responsibilities and put the team in a group chat so handoffs stay visible.

Keep the brief and task board in a shared project folder. Give every task one owner, its dependencies, acceptance checks, and an expected output.

Run independent investigations in parallel. Assign file ownership before edits and serialize changes that touch the same files.

Use scripts for repeatable checks. Preserve raw logs, but pass compact results and links between Bots.

Keep successful work when a step fails. Return the specific failure for correction and stop after two failed attempts.

Have QA inspect the resulting patch against the brief. The lead returns the diff, test evidence, and unresolved issues.

Show me the proposed configuration before applying it. Require my approval before merging, deploying, or changing production.

Never send, post, spend, or buy without my explicit yes.

التشغيل الأول

  1. 1Read https://x.com/Solomonrojie/status/2114860139819798907 (credit @Solomonrojie).
  2. 2Paste the author-quoted lead + security/performance/QA setup prompt.
  3. 3Review the proposed bots, group chat, and task-board shape before applying.
  4. 4Let specialists investigate in parallel; lead returns diff + test evidence + unresolved issues.
  5. 5You press approve only when ready to merge, deploy, or change production.

حاجز الموافقة

Show config first; you approve before merging, deploying, or changing production.

ما الذي تعدّله

Steal the quoted lead+3 prompt; keep merge/deploy behind your OK.

المصدر

Solomon Rojie @Solomonrojie · المنشور الأصلي

غير تابع لـ xAI. لم نكتب هذا النص التوجيهي. تبقى شروط القوالب التابعة لطرف ثالث سارية.

تصفح القوالب

تصفح مخططات الفرق

حزمة Pro

تريد الإعداد الكامل، لا الفكرة فقط؟

تمنحك حزم Pro وصف الوظيفة والنصوص التوجيهية والجداول والمزالق لحالات الاستخدام الشائعة.

اطلع على Pro