@electric-agent/agent 1.1.0 → 1.1.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@electric-agent/agent",
-  "version": "1.1.0",
+  "version": "1.1.7",
   "description": "CLI tool that turns natural-language app descriptions into running reactive Electric SQL + TanStack DB applications",
   "type": "module",
   "bin": {
@@ -27,8 +27,8 @@
     "commander": "^13.1.0",
     "dotenv": "^17.3.1",
     "zod": "^3.24.1",
-    "@electric-agent/protocol": "1.2.0",
-    "@electric-agent/studio": "1.3.0"
+    "@electric-agent/studio": "1.5.0",
+    "@electric-agent/protocol": "1.3.0"
   },
   "devDependencies": {
     "@types/node": "^22.15.0",

package/template/.claude/skills/create-app/SKILL.md

@@ -20,13 +20,9 @@ Evaluate the description provided in `$ARGUMENTS`.
 - 50-79: Recognizable app type but light on specifics
 - 0-49: Too vague to proceed
 
-**If the description scores below 70**, use AskUserQuestion to ask 1-3 targeted questions:
-- What are the key features or interactions? (e.g., drag-and-drop, categories, search, due dates)
-- What are the main entities/data objects and their relationships?
-- Should it support multi-user collaboration with real-time sync?
-- Should it work offline and sync when reconnected?
+**If the description scores below 70**, use AskUserQuestion to gather missing details. You can use any combination of formats — single or multiple questions, multiSelect for picking features, headers to group topics, or free-text for open-ended input. Choose whatever format best fits the gaps in the description. Keep questions specific to the described app type.
 
-Keep questions specific to the described app type. After getting answers, enrich the description mentally and proceed.
+After getting answers, enrich the description mentally and proceed.
 
 **If the description scores 70+**, proceed immediately without questions.
 
@@ -85,6 +81,10 @@ export const entityName = pgTable("entity_name", {
 ### Phase 6: Architecture Reference
 - [ ] Write ARCHITECTURE.md
 
+### Phase 7: Deploy & Preview
+- [ ] Run migrations (drizzle-kit generate && drizzle-kit migrate)
+- [ ] pnpm dev:start
+
 ## Design Conventions
 - UUID primary keys with defaultRandom()
 - timestamp({ withTimezone: true }) for all dates
@@ -240,6 +240,18 @@ _Last updated: [ISO date]_
 ## State & Context
 ```
 
+## Phase 8: Deploy & Preview
+
+Start the dev server so the user can preview the app:
+
+```bash
+pnpm dev:start
+```
+
+**IMPORTANT**: Always use `pnpm dev:start` from the project directory. Do NOT use `sprite-env services create` or launch Vite manually — the project's `vite.config.ts` contains required settings (`allowedHosts`, `port`, `proxy`) that will not be applied if Vite is started from a different directory.
+
+After starting, the app is accessible at the preview URL (shown in the UI).
+
 ## Critical Rules (from electric-app-guardrails)
 
 - `z` from `"zod/v4"` — NEVER from `"zod"`
@@ -273,7 +285,9 @@ When the app runs inside a cloud sandbox (Fly.io Sprite), the following constrai
 - **The preview URL** follows the pattern: `https://<sprite-name>.sprites.app`
 - **`vite.config.ts` is pre-configured** with `port`, `host: true`, `allowedHosts: true`, and the Electric proxy — **DO NOT MODIFY it**. Changing it WILL break the preview.
 
-The `pnpm dev:start` script starts the Vite dev server in the background on the correct port. After finishing all code generation, always run migrations then `pnpm dev:start` so the user can preview.
+**ALWAYS use `pnpm dev:start`** to start the dev server. This script runs Vite from the project directory where `vite.config.ts` is located. **DO NOT use `sprite-env services create`** or launch Vite manually — doing so will start Vite from the wrong directory, causing it to miss the config and reject Sprite hostnames with `allowedHosts` errors.
+
+After finishing all code generation, always run migrations then `pnpm dev:start` so the user can preview.
 
 ## Scaffold Files (DO NOT MODIFY)