@yottagraph-app/aether-instructions 1.1.29 → 1.1.31

package/commands/build_my_app.md

@@ -210,7 +210,7 @@ Implement the plan:
 
 ---
 
-## Step 7: Verify
+## Step 7: Verify and Commit
 
 After building, check dependencies are installed and run a build:
 
@@ -221,15 +221,46 @@ npm run build
 
 Fix any build errors.
 
-Then suggest the user run `npm run dev` to preview their app locally.
+Then format and commit:
+
+```bash
+npm run format
+git add -A
+git commit -m "[Agent commit] Initial app build from project brief"
+```
+
+**Push directly to main.** Vercel auto-deploys on push to main, so this
+gets the app live immediately. Do NOT try to create a pull request via
+`gh pr create` — in Cursor Cloud environments, the GitHub integration
+token lacks PR permissions (known Cursor issue). Pushing to main is the
+correct workflow.
+
+```bash
+git push origin main
+```
+
+If running locally (not in Cursor Cloud), the user may prefer a PR-based
+workflow — ask before pushing directly to main in that case.
 
 ---
 
-## Step 8: Next Steps
+## Step 8: Deploy Agents and Next Steps
+
+If the app includes agents in `agents/`, offer to deploy them now:
+
+> Your app is built! I see you have an agent in `agents/`. Want me to
+> deploy it now? I can run the deployment for you.
+
+If the user agrees (or if this is an automated build), run `/deploy_agent`
+to deploy each agent. Don't just tell the user to type the command — do it
+for them.
+
+Then present next steps:
 
-> Your app is taking shape! Here's what you can do next:
+> Here's what you can do next:
 >
 > - **Preview locally** with `npm run dev`
 > - **Push to deploy** -- Vercel auto-deploys on push to main
-> - **Deploy an AI agent** -- run `/deploy_agent` when you have an agent ready
-> - **Deploy an MCP server** -- run `/deploy_mcp` for tool servers
+> - **Deploy agents** -- I can deploy them for you, or use the Deploy
+>   button on the Broadchurch portal's project page
+> - **Deploy MCP servers** -- same as above, from the portal or ask me

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@yottagraph-app/aether-instructions",
-    "version": "1.1.29",
+    "version": "1.1.31",
     "description": "Cursor rules, commands, and skills for Aether development",
     "files": [
         "rules",

package/variants/mcp-only/commands/build_my_app.md

@@ -121,7 +121,7 @@ Match the brief: dashboards from `/api/...`, **chat** as primary, or both. No El
 
 ---
 
-## Step 7: Verify
+## Step 7: Verify and Commit
 
 After building, ensure dependencies are installed and run a production build:
 
@@ -130,17 +130,48 @@ test -d node_modules || npm install
 npm run build
 ```
 
-Fix any build errors. Then suggest the user run `npm run dev` to preview locally.
+Fix any build errors. Then format and commit:
+
+```bash
+npm run format
+git add -A
+git commit -m "[Agent commit] Initial app build from project brief"
+```
+
+**Push directly to main.** Vercel auto-deploys on push to main, so this
+gets the app live immediately. Do NOT try to create a pull request via
+`gh pr create` — in Cursor Cloud environments, the GitHub integration
+token lacks PR permissions (known Cursor issue). Pushing to main is the
+correct workflow.
+
+```bash
+git push origin main
+```
+
+If running locally (not in Cursor Cloud), the user may prefer a PR-based
+workflow — ask before pushing directly to main in that case.
 
 Deploy agents as needed; if the brief relies on **materialized** data, run or schedule the relevant agents before expecting full UI data.
 
 ---
 
-## Step 8: Next steps
+## Step 8: Deploy Agents and Next Steps
+
+If the app includes agents in `agents/`, offer to deploy them now:
+
+> Your app is built! I see you have an agent in `agents/`. Want me to
+> deploy it now? I can run the deployment for you.
+
+If the user agrees (or if this is an automated build), run `/deploy_agent`
+to deploy each agent. Don't just tell the user to type the command — do it
+for them. Ensure MCP is configured for the agent runtime per `agents-data`.
+
+Then present next steps:
 
-> Your app is taking shape. Suggested follow-ups:
+> Here's what you can do next:
 >
 > - **Preview locally** with `npm run dev`
 > - **Push to deploy** — Vercel auto-deploys on push to main
-> - **Agents** — run `/deploy_agent` when an agent is ready; ensure MCP is configured for the agent runtime per `agents-data`
-> - **MCP servers** — run `/deploy_mcp` if you add custom tool servers
+> - **Deploy agents** — I can deploy them for you, or use the Deploy
+>   button on the Broadchurch portal's project page
+> - **MCP servers** — same as above, from the portal or ask me