create-zenbu-app 0.0.35 → 0.0.36

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-zenbu-app",
-  "version": "0.0.35",
+  "version": "0.0.36",
   "description": "Scaffold a new Zenbu app",
   "type": "module",
   "publishConfig": {
@@ -45,7 +45,7 @@
   "scripts": {
     "test:desktop": "bash scripts/test-desktop.sh",
     "build": "pnpm run build:agents && tsdown",
-    "build:agents": "sh -c 'for d in vanilla tailwind plugin; do { printf \"# Zenbu.js docs\\n\\n\"; curl -fsSL https://zenbulabs.mintlify.app/llms-full.txt; printf \"\\n\\n# General rules\\n\\n- never use any, every api in the app is fully type safe\\n- use zen link after making changes to sync types if it did not happen automatically\\n- always use <pm> run db:generate after making a schema change otherwise it will not take affect\\n- always prefer to make db updates via the replica so that updates are instant. if you used rpc to update a replica it would serve 0 purpose and just add an extra round trip\\n- prefer one component per file\\n\"; } > templates/$d/AGENTS.md; done'",
+    "build:agents": "sh -c 'for d in vanilla tailwind plugin; do { printf \"# Zenbu.js docs\\n\\n\"; if [ \"$d\" = plugin ]; then printf \"# Plugin rules\\n\\n- do not add this plugin to the host config (the plugins array in zenbu.config.ts, a zenbu.local.ts overlay, or any zenbu.plugins*.jsonc manifest). build it in its own folder and leave it there. the user enables or installs it themselves when they are ready, or will ask you to. do not edit their config files on your own.\\n\\n\"; fi; curl -fsSL https://zenbulabs.mintlify.app/llms-full.txt; printf \"\\n\\n# General rules\\n\\n- never use any, every api in the app is fully type safe\\n- use zen link after making changes to sync types if it did not happen automatically\\n- always use <pm> run db:generate after making a schema change otherwise it will not take affect\\n- always prefer to make db updates via the replica so that updates are instant. if you used rpc to update a replica it would serve 0 purpose and just add an extra round trip\\n- prefer one component per file\\n\"; } > templates/$d/AGENTS.md; done'",
     "typecheck": "tsc --noEmit -p tsconfig.json"
   }
 }

package/templates/plugin/AGENTS.md

@@ -1,5 +1,9 @@
 # Zenbu.js docs
 
+# Plugin rules
+
+- do not add this plugin to the host config (the plugins array in zenbu.config.ts, a zenbu.local.ts overlay, or any zenbu.plugins*.jsonc manifest). build it in its own folder and leave it there. the user enables or installs it themselves when they are ready, or will ask you to. do not edit their config files on your own.
+
 # Overview
 Source: https://zenbulabs.mintlify.app/api-reference/overview
 
@@ -1387,15 +1391,15 @@ Source: https://zenbulabs.mintlify.app/introduction
 
 
 
-Zenbu.js is a framework for building hackable desktop apps.
+Zenbu.js is the framework for building extensible applications, powering [Zenbu](https://zenbu.dev).
 
-Apps built with Zenbu.js are designed to be modified after they ship. Users can edit the source code directly, or install plugins that extend the app with new functionality.
+Apps and plugins built with Zenbu.js are designed to be modified after they are installed. Users can edit the source code directly, or install plugins that extend the app with new functionality.
 
-The framework also handles the hard parts of desktop development for you, like syncing state between processes, RPC, and hot-reloading everything as you make changes.
+The SDK also handles the hard parts of application development, like syncing state between processes, RPC, and hot-reloading everything as you make changes.
 
-### Why build a hackable app
+### Why build with Zenbu.js
 
-* Coding agents can generate and customize software on demand for a specific use case. A hackable app gives them full access to do that.
+* Coding agents can generate and customize software on demand for a specific use case. An app built on Zenbu.js gives them full access to do that.
 * Letting people modify your app means more directions get explored than you could reach on your own.
 * Extensible code tends to be more maintainable, because it's already written to be changed.
 

package/templates/tailwind/AGENTS.md

@@ -1387,15 +1387,15 @@ Source: https://zenbulabs.mintlify.app/introduction
 
 
 
-Zenbu.js is a framework for building hackable desktop apps.
+Zenbu.js is the framework for building extensible applications, powering [Zenbu](https://zenbu.dev).
 
-Apps built with Zenbu.js are designed to be modified after they ship. Users can edit the source code directly, or install plugins that extend the app with new functionality.
+Apps and plugins built with Zenbu.js are designed to be modified after they are installed. Users can edit the source code directly, or install plugins that extend the app with new functionality.
 
-The framework also handles the hard parts of desktop development for you, like syncing state between processes, RPC, and hot-reloading everything as you make changes.
+The SDK also handles the hard parts of application development, like syncing state between processes, RPC, and hot-reloading everything as you make changes.
 
-### Why build a hackable app
+### Why build with Zenbu.js
 
-* Coding agents can generate and customize software on demand for a specific use case. A hackable app gives them full access to do that.
+* Coding agents can generate and customize software on demand for a specific use case. An app built on Zenbu.js gives them full access to do that.
 * Letting people modify your app means more directions get explored than you could reach on your own.
 * Extensible code tends to be more maintainable, because it's already written to be changed.
 

package/templates/vanilla/AGENTS.md

@@ -1387,15 +1387,15 @@ Source: https://zenbulabs.mintlify.app/introduction
 
 
 
-Zenbu.js is a framework for building hackable desktop apps.
+Zenbu.js is the framework for building extensible applications, powering [Zenbu](https://zenbu.dev).
 
-Apps built with Zenbu.js are designed to be modified after they ship. Users can edit the source code directly, or install plugins that extend the app with new functionality.
+Apps and plugins built with Zenbu.js are designed to be modified after they are installed. Users can edit the source code directly, or install plugins that extend the app with new functionality.
 
-The framework also handles the hard parts of desktop development for you, like syncing state between processes, RPC, and hot-reloading everything as you make changes.
+The SDK also handles the hard parts of application development, like syncing state between processes, RPC, and hot-reloading everything as you make changes.
 
-### Why build a hackable app
+### Why build with Zenbu.js
 
-* Coding agents can generate and customize software on demand for a specific use case. A hackable app gives them full access to do that.
+* Coding agents can generate and customize software on demand for a specific use case. An app built on Zenbu.js gives them full access to do that.
 * Letting people modify your app means more directions get explored than you could reach on your own.
 * Extensible code tends to be more maintainable, because it's already written to be changed.