@yottagraph-app/aether-instructions 1.1.30 → 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,7 +221,26 @@ 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.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@yottagraph-app/aether-instructions",
-    "version": "1.1.30",
+    "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,7 +130,26 @@ 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.