framer-dalton 0.0.25 → 0.0.27

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 (6) hide show
  1. package/README.md +1 -1
  2. package/dist/cli.js +346 -311
  3. package/dist/start-relay-server.js +111 -27
  4. package/docs/skills/framer-project.md +36 -19
  5. package/docs/skills/framer.md +1 -1
  6. package/package.json +8 -7
package/README.md CHANGED
@@ -23,7 +23,7 @@ The CLI and the installed skills are meant to work together. There are three ski
23
23
  1. Running `npx framer-dalton@latest setup` will install the base `framer` and `framer-code-components` skills.
24
24
  2. The frontmatter of `framer-code-components` tells agents to always load `framer` and the generated project skill first.
25
25
  3. The frontmatter of `framer` tells agents to run `npx framer-dalton@latest setup` BEFORE loading the skill. This command will auto-update the cli and update the skill files.
26
- 4. Creating a new session for a project will create a `framer-project-<project id>` file. This file contains the latest agent system prompt from `framer.getAgentSystemPrompt` and the latest project context from `framer.getAgentContext`. Agents must load this project-specific skill immediately after creating a session before doing any connected-project work.
26
+ 4. Creating a new session for a project will create a `framer-project-<project id>` file. This file contains the latest agent system prompt from `framer.agent.getSystemPrompt` and the latest project context from `framer.agent.getContext`. Agents must load this project-specific skill immediately after creating a session before doing any connected-project work.
27
27
 
28
28
  ## Local Development
29
29