@yottagraph-app/aether-instructions 1.1.29 → 1.1.30

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/commands/build_my_app.md +16 -4
  2. package/package.json +1 -1
  3. package/variants/mcp-only/commands/build_my_app.md +16 -4
package/commands/build_my_app.md CHANGED
@@ -225,11 +225,23 @@ Then suggest the user run `npm run dev` to preview their app locally.
225
225
 
226
226
  ---
227
227
 
228
- ## Step 8: Next Steps
228
+ ## Step 8: Deploy Agents and Next Steps
229
229
 
230
- > Your app is taking shape! Here's what you can do next:
230
+ If the app includes agents in `agents/`, offer to deploy them now:
231
+
232
+ > Your app is built! I see you have an agent in `agents/`. Want me to
233
+ > deploy it now? I can run the deployment for you.
234
+
235
+ If the user agrees (or if this is an automated build), run `/deploy_agent`
236
+ to deploy each agent. Don't just tell the user to type the command — do it
237
+ for them.
238
+
239
+ Then present next steps:
240
+
241
+ > Here's what you can do next:
231
242
  >
232
243
  > - **Preview locally** with `npm run dev`
233
244
  > - **Push to deploy** -- Vercel auto-deploys on push to main
234
- > - **Deploy an AI agent** -- run `/deploy_agent` when you have an agent ready
235
- > - **Deploy an MCP server** -- run `/deploy_mcp` for tool servers
245
+ > - **Deploy agents** -- I can deploy them for you, or use the Deploy
246
+ > button on the Broadchurch portal's project page
247
+ > - **Deploy MCP servers** -- same as above, from the portal or ask me
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@yottagraph-app/aether-instructions",
3
- "version": "1.1.29",
3
+ "version": "1.1.30",
4
4
  "description": "Cursor rules, commands, and skills for Aether development",
5
5
  "files": [
6
6
  "rules",
package/variants/mcp-only/commands/build_my_app.md CHANGED
@@ -136,11 +136,23 @@ Deploy agents as needed; if the brief relies on **materialized** data, run or sc
136
136
 
137
137
  ---
138
138
 
139
- ## Step 8: Next steps
139
+ ## Step 8: Deploy Agents and Next Steps
140
140
 
141
- > Your app is taking shape. Suggested follow-ups:
141
+ If the app includes agents in `agents/`, offer to deploy them now:
142
+
143
+ > Your app is built! I see you have an agent in `agents/`. Want me to
144
+ > deploy it now? I can run the deployment for you.
145
+
146
+ If the user agrees (or if this is an automated build), run `/deploy_agent`
147
+ to deploy each agent. Don't just tell the user to type the command — do it
148
+ for them. Ensure MCP is configured for the agent runtime per `agents-data`.
149
+
150
+ Then present next steps:
151
+
152
+ > Here's what you can do next:
142
153
  >
143
154
  > - **Preview locally** with `npm run dev`
144
155
  > - **Push to deploy** — Vercel auto-deploys on push to main
145
- > - **Agents** — run `/deploy_agent` when an agent is ready; ensure MCP is configured for the agent runtime per `agents-data`
146
- > - **MCP servers** — run `/deploy_mcp` if you add custom tool servers
156
+ > - **Deploy agents** — I can deploy them for you, or use the Deploy
157
+ > button on the Broadchurch portal's project page
158
+ > - **MCP servers** — same as above, from the portal or ask me