@phren/cli 0.0.41 → 0.0.43

package/skills/sync/SKILL.md

@@ -102,7 +102,7 @@ If this fails (not a git repo, no remote), tell the user. Don't silently skip.
 Run init against the pulled phren repo so hooks, MCP registration, and machine/profile wiring are refreshed:
 
 ```bash
-PHREN_PATH="$PHREN_DIR" npx phren init -y
+PHREN_PATH="$PHREN_DIR" phren init -y
 ```
 
 If the user is in an untracked repo afterward, tell them to open a session there and let the agent ask, or run `phren add` from that directory.

package/starter/README.md

@@ -32,7 +32,7 @@ New to phren? Here's what each file does and when it matters.
 
 **FINDINGS.md** fills itself. As Claude discovers insights, patterns, and decisions during your sessions, it tells phren and entries land here grouped by date. Old entries fade from retrieval over time. Wrong entries can be removed with `remove_finding()`.
 
-**tasks.md** is your task board file. It keeps Active (working now), Queue (up next), and Done (finished) in one place so the work history stays with the project. You can also manage it from `npx phren shell`.
+**tasks.md** is your task board file. It keeps Active (working now), Queue (up next), and Done (finished) in one place so the work history stays with the project. You can also manage it from `phren shell`.
 
 **global/CLAUDE.md** applies everywhere. Your style preferences, tool choices, things Claude should always know regardless of which project you're in.
 
@@ -40,14 +40,14 @@ New to phren? Here's what each file does and when it matters.
 
 ## Getting started
 
-If you got here via `npx phren init`, you're already set up. Restart Claude Code and you're good.
+If you got here via `npx @phren/cli init`, you're already set up. Restart Claude Code and you're good.
 
 If you cloned manually:
 
-1. Add the MCP server: `claude mcp add phren -- npx phren ~/.phren`
+1. Add the MCP server: `claude mcp add phren -- npx @phren/cli ~/.phren`
 2. Install skills: `/plugin marketplace add alaarab/phren` then `/plugin install phren@phren`
 3. Restart Claude Code
-4. Add a project: run `/phren-init my-project` or scaffold one with a template such as `npx phren init --template python-project`
+4. Add a project: run `/phren-init my-project` or scaffold one with a template such as `phren init --template python-project`
 5. Push to a private GitHub repo to sync across machines
 
 ## Day-to-day workflow
@@ -56,7 +56,7 @@ If you cloned manually:
 2. **Work normally**: Claude reads your project docs and builds on what phren remembers
 3. **Fragments accumulate**: tell phren what you learned, or he picks up insights automatically
 4. **Session ends**: phren commits and pushes what he collected
-5. **Review occasionally**: run `npx phren shell` to triage what phren queued, manage tasks, and check health
+5. **Review occasionally**: run `phren shell` to triage what phren queued, manage tasks, and check health
 
 ## Syncing across machines
 
@@ -71,4 +71,4 @@ Each profile in `profiles/` lists which projects that machine should see. After
 
 ## Troubleshooting
 
-Run `npx phren doctor --fix` to check and repair your setup.
+Run `phren doctor --fix` to check and repair your setup.

package/starter/machines.yaml

@@ -5,4 +5,4 @@
 #   work-laptop: work
 #   home-desktop: personal
 #
-# After adding a line, run: npx phren init
+# After adding a line, run: phren init

package/starter/my-first-project/tasks.md

@@ -22,4 +22,4 @@
 
 ## Done
 
-- [x] Run `npx phren init` to set up phren
+- [x] Run `phren init` to set up phren

package/starter/templates/README.md

@@ -1,6 +1,6 @@
 # starter/templates/
 
-Project templates bundled in the npm package, used by `npx phren init --template <name>`.
+Project templates bundled in the npm package, used by `phren init --template <name>`.
 
 Each subdirectory (frontend, library, monorepo, python-project) contains pre-filled project files with sensible defaults for that project type. When a user runs init with `--template`, these files are copied into their `~/.phren/<project>/` directory. For other project types, adaptive init infers topics and structure from repo content.