@use-aistack/cli 0.3.0 → 0.5.0

package/README.md

@@ -1,26 +1,56 @@
 # @use-aistack/cli
 
-Share and clone AI development configurations (prompts, rules, skills, MCP setups).
+Measure and share your AI stack. The CLI scans your local Claude Code transcripts, shows you exactly what would go up, and publishes only after you approve in your terminal.
 
 Run on-demand with `npx` — no install required:
 
 ```sh
-npx @use-aistack/cli <command>
+npx @use-aistack/cli sync
 ```
 
 ## Commands
 
+### `npx @use-aistack/cli sync`
+
+The default command. Scan your local transcripts (rolling 30 days), review the full summary, and publish the measured layer to your stack. Nothing leaves your machine without your explicit approval at the prompt. Raw transcripts, prompts, and paths never leave at all — only aggregates.
+
+```sh
+npx @use-aistack/cli sync
+```
+
+Requires a one-time `login` first.
+
+### `npx @use-aistack/cli sync --auto on` / `off`
+
+Optional: keep your stack fresh without manual syncs. `on` writes a `SessionStart` hook (`async: true`) into `~/.claude/settings.json`. The hook runs a silent sync at most once per day when a Claude Code session starts. `off` removes the hook and revokes the standing opt-in.
+
+```sh
+npx @use-aistack/cli sync --auto on            # enable, default every 24h
+npx @use-aistack/cli sync --auto on --every 12 # custom frequency in hours
+npx @use-aistack/cli sync --auto off           # revoke
+```
+
+The silent run (`sync --auto`) never prompts and publishes only under this opt-in. Each run appends one line to `~/.config/aistack/sync.log` (capped at 200 lines). The next interactive `sync` reports the last result. After 3 failures in a row, one visible message appears in Claude Code and names the fix. No email, no dialogs.
+
 ### `npx @use-aistack/cli login`
 
-Authenticate with your AI Stack account via browser.
+Link this machine to your AI Stack account via browser.
 
 ```sh
 npx @use-aistack/cli login
 ```
 
+### `npx @use-aistack/cli connect claude`
+
+Optional: install the in-session sync surface for Claude Code — the `aistack` MCP server (user scope) plus the `aistack-sync` Skill. After that, say "sync my stack" in any Claude Code session. Both halves install together or not at all.
+
+```sh
+npx @use-aistack/cli connect claude
+```
+
 ### `npx @use-aistack/cli collect`
 
-Scan your project for AI config files and upload them.
+Scan your project for AI config files (prompts, rules, skills, MCP setups) and upload them to your stack.
 
 ```sh
 cd your-project
@@ -29,12 +59,12 @@ npx @use-aistack/cli collect
 
 Detects: `.cursorrules`, `CLAUDE.md`, `AGENTS.md`, `.cursor/rules/`, `mcp.json`, skill directories, prompts, and global configs (`~/.claude/`, `~/.cursor/`, etc).
 
-### `npx @use-aistack/cli create <slug>`
+### `npx @use-aistack/cli create`
 
-Clone a shared project's AI config files into your current directory.
+Write your stack's AI config files into the current directory.
 
 ```sh
-npx @use-aistack/cli create my-project-abc123
+npx @use-aistack/cli create
 ```
 
 ## Install globally (optional)
@@ -49,8 +79,8 @@ Then the same commands become:
 
 ```sh
 aistack login
+aistack sync
 aistack collect
-aistack create <slug>
 ```
 
 ## Development
@@ -64,8 +94,7 @@ Test locally:
 
 ```sh
 node packages/cli/dist/index.js login
-node packages/cli/dist/index.js collect
-node packages/cli/dist/index.js create <slug>
+node packages/cli/dist/index.js sync
 ```
 
 Set `AISTACK_URL=http://localhost:3019` to test against local dev server.