Grok for the idea, Grok Bot for the direction, Cursor for the code

インストールまたは作成するもの

Brainstorm in Grok, then pass it to your primary bot, which creates one bot per app. That project bot writes the spec, file structure, and a starter prompt — not the codebase. It makes a GitHub repo, opens it in Cursor, and pastes the starter prompt so Cursor builds it. When you're stuck, the project bot writes a fix plan and drops it back into Cursor. Code stays in Cursor and the repo.

プロンプト

1. I brainstorm everything with Grok first.
2. Pass it onto Primary Grok Bot
3. Asks Primary Bot to create bot for specific project(app)
4. That project bot writes the spec, the file structure, and a starter prompt. It does not write the whole codebase.
5. The bot will make a new GitHub repo, clone it, and open it in Cursor
6. It will paste the starter prompt into Cursor and let Cursor build it. Commits stay in that repo.
7. When I get stuck, I ask the project bot for a fix plan, then drop that plan back into Cursor. Code stays in Cursor, not in the bot.

初回実行

1. 1Read https://x.com/B_doong2daddy/status/2107298546865090737 (credit @B_doong2daddy).
2. 2Brainstorm the app in Grok, then hand the result to your primary bot.
3. 3Ask the primary bot to create a bot just for this app.
4. 4Have that project bot write the spec, file structure, and a starter prompt — not the code — then set up a GitHub repo and open it in Cursor.
5. 5Let Cursor build from the starter prompt; when stuck, ask the project bot for a fix plan and paste it back into Cursor.

調整ポイント

One bot per project keeps direction clear; letting Cursor own the code keeps the bot light.

出典

Texas Twins Dad @B_doong2daddy · 元の投稿

xAI とは提携していません。このプロンプトは当サイトが書いたものではありません。第三者テンプレートの規約も適用されます。