framer-dalton 0.0.18 → 0.0.21

package/docs/skills/framer-canvas-editing-project.md

@@ -25,8 +25,8 @@ allowed-tools: ["Bash(npx framer-dalton:*)", "Bash(npx framer-dalton@latest:*)",
 ## Workflow Loop
 
 ```bash
-# 1) Read page structure first
-npx framer-dalton read-project -s <sessionId> -q '<get page structure>' -p "/"
+# 1) Read page structure first (fill in real query from Live Agent System Prompt)
+npx framer-dalton read-project -s <sessionId> -q '<query to get page structure>' -p "/"
 
 # 2) Request additional targeted queries only if needed
 

package/docs/skills/framer.md

@@ -46,12 +46,26 @@ npx framer-dalton project list
 
 Use that list to infer the likely project from the names and recency. If the right project is already known, use its project ID with `session new`. If there are multiple possible matches, clarify with the user. Only ask the user for a Project URL if there is no clear match. Avoid talking about the technical contents of returned data like IDs.
 
-Create a session:
+Create a session against an existing project:
 
 ```bash
 npx framer-dalton session new "<url or id>"
 ```
 
+To create a brand new empty project and connect to it:
+
+```bash
+npx framer-dalton project new
+npx framer-dalton session new "<returned project id>"
+```
+
+To remix (duplicate) an existing project and connect to the copy:
+
+```bash
+npx framer-dalton project remix "<url, project id, or remix link>"
+npx framer-dalton session new "<returned project id>"
+```
+
 Note that during beta, you cannot connect to non-beta projects. If creating a session errors with a message about this, you need to move your project to beta.
 
 #### 2. Look up the API (before EVERY code execution)
@@ -65,7 +79,7 @@ npx framer-dalton docs Collection.getItems  # What are the parameters and return
 
 #### 3. Execute code
 
-Only after checking docs, write your code to a unique file under `{{FRAMER_TEMPORARY_DIR}}/` and execute with `-f`. Name each file `<sessionId>-<short-summary>.js` where `<short-summary>` is a brief kebab-case description (e.g., `1-read-collections.js`, `1-add-team-member.js`). Files are automatically deleted after execution.
+Only after checking docs, write your code to a unique file under `{{FRAMER_TEMPORARY_DIR}}/` and execute with `-f`. Name each file `<sessionId>-<short-summary>.js` where `<short-summary>` is a brief kebab-case description (e.g., `1-read-collections.js`, `1-add-team-member.js`).
 
 ```bash
 npx framer-dalton exec -s 1 -f {{FRAMER_TEMPORARY_DIR}}/1-read-collections.js
@@ -81,6 +95,11 @@ Always save results you'll need again. Don't repeat API calls.
 
 - Be concise. Don't narrate implementation details like field IDs, escaping, or internal steps. Just do the work and report what was accomplished in user-facing terms.
 - Use `framer.*` for plugin API calls. Top-level methods are not globals.
+- Before making changes that add/update/delete content that the user has not clearly and explicitly requested in this conversation, inform the user of what you plan to do and why, and ask them to confirm.
+    - You do not need to ask for confirmation when carrying out a specific add/update/delete change that the user has already clearly requested (this counts as explicit consent).
+    - You do not need to explain or ask for confirmation for non-destructive calls like reading project state.
+    - If the exact action was not agreed upon, or you are inferring a broader change or choosing between multiple reasonable options using your own judgment, ask for confirmation.
+    - Always ask for confirmation before destructive actions that the user did not explicitly request - especially deletes, cleanup, resets, or broad removals inferred by the agent.
 
 ## Context Variables
 
@@ -142,11 +161,7 @@ npx framer-dalton session list
 
 ## Canvas Editing
 
-For design tasks, do not try to build or restyle pages with low-level node APIs. Instead, load the dynamically created project-scoped canvas skill and use the `read-project` and `apply-changes` subcommands.
-
-After session creation, load the dynamically created project-scoped skill `framer-canvas-editing-project-<projectId>` for canvas editing on the connected project. It contains the canvas editing guidance, the live agent system prompt, and the live project context for `pagePath: "/"`.
-
-Do not call `framer.startAgentConversation()` or `framer.continueAgentConversation()` with this approach.
+For design tasks, do not try to build or restyle pages with low-level node APIs. Instead, after session creation, load the dynamically created project-scoped skill `framer-canvas-editing-project-<projectId>` for canvas editing on the connected project. It contains the canvas editing guidance and all related documentation for how to use the relevant methods.
 
 ## Canvas Editing: Alternative Approach (“Prompt the Framer agent”)
 

package/package.json

@@ -1,10 +1,8 @@
 {
   "name": "framer-dalton",
-  "version": "0.0.18",
+  "version": "0.0.21",
   "type": "module",
-  "bin": {
-    "framer-dalton": "./dist/cli.js"
-  },
+  "bin": "./dist/cli.js",
   "main": "./dist/cli.js",
   "types": "./dist/cli.d.ts",
   "files": [
@@ -25,15 +23,20 @@
     "@trpc/client": "^11.9.0",
     "@trpc/server": "^11.9.0",
     "commander": "^12.1.0",
-    "framer-api": "^0.1.4-alpha.1",
+    "framer-api": "0.1.7",
     "zod": "^4.3.6"
   },
   "devDependencies": {
     "@biomejs/biome": "^2.3.13",
+    "@framerjs/framer-events": "0.0.175",
     "@types/node": "24.10.9",
     "tsup": "^8.0.2",
     "tsx": "^4.19.0",
     "typescript": "^5.9.2",
     "vitest": "^4.0.18"
+  },
+  "packageManager": "yarn@4.13.0",
+  "engines": {
+    "node": ">=22"
   }
 }