pi-chrome 0.15.2: recipe prompts in user-language (no tool names)

4 files changed, 15 insertions, 12 deletions

diff --git a/CHANGELOG.md b/CHANGELOG.md
index f3f3475..a782e0a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,10 @@
 
 All notable user-facing changes to `pi-chrome`.
 
+## 0.15.2 — 2026-05-13
+
+- **Recipe prompts rewritten in user-language.** Earlier recipes leaked tool names into the `You:` prompts ("Use `chrome_tab list` to find my GitHub notifications tab…"), implying users need to know the tool catalog before they can ask anything. Prompts now read as natural intent; the agent trace below each one still shows the `chrome_*` primitives the agent picked. Affects the 30-second try-this block, all 3 hero recipes (PR triage / Linear standup / Bug repro), and 3 of the 6 collapsed recipes (auth-only data pull, network forensics, file upload).
+
 ## 0.15.1 — 2026-05-13
 
 - **Architecture diagram now renders on pi.dev.** Replaced Unicode box-drawing characters (`┌─┐│└┘┬▼`) with plain ASCII (`+ - | v`). Pi.dev's monospace font was dropping the horizontal `─` glyphs, leaving the diagram as floating vertical bars. ASCII renders everywhere.
diff --git a/README.md b/README.md
index 5babafd..7846f31 100644
--- a/README.md
+++ b/README.md
@@ -52,10 +52,9 @@ pi-chrome v<version>
 ## Try this in 30 seconds after install
 
 ```text
-Use chrome_tab list to find my GitHub notifications tab.
-chrome_snapshot it, then write a 5-bullet triage:
-which PRs need my review today, sorted by staleness.
-Do not click anything yet.
+Look at my GitHub notifications tab and triage which PRs
+need my review today, sorted by staleness.
+Don't click anything yet — just read and summarize.
 ```
 
 You'll watch the agent jump to your GitHub tab and read the page — using **your** session, **your** filters, **your** orgs.
@@ -69,7 +68,7 @@ Each recipe assumes the relevant tab is already open in the Chrome you control.
 **PR triage**
 
 ```text
-You:    "Use chrome_tab list to find my GitHub notifications tab, then summarize PRs needing my review today, sorted by staleness."
+You:    "Look at my GitHub notifications tab and summarize the PRs needing my review today, sorted by staleness."
 Agent:  chrome_tab(list) → chrome_snapshot(uid:el-notifications) → chrome_evaluate(...)
         ✓ 7 PRs waiting on you. 2 stale >3d (storage-rewrite, billing-v2).
           1 just turned CI-green (api-keys-prune). Full sorted list below.
@@ -79,7 +78,7 @@ You:    [pastes the list straight into Linear]
 **Linear standup**
 
 ```text
-You:    "Open my Linear current cycle in the active tab and write a 5-bullet standup."
+You:    "Open my Linear current cycle and write a 5-bullet standup from it."
 Agent:  chrome_tab(activate, urlIncludes:"linear.app") → chrome_snapshot(uid:el-cycle) → chrome_evaluate(...)
         ✓ 5 in-progress, 2 blocked. Standup draft:
           • Shipped: bridge auto-recover.   • In flight: trusted-mode retry path.
@@ -91,7 +90,7 @@ You:    [drops it into #standup]
 **Bug repro with evidence**
 
 ```text
-You:    "Repro the checkout 500 on staging, save a screenshot at each step under ./repro/."
+You:    "Reproduce the checkout 500 on staging. Save a screenshot at each step under ./repro/."
 Agent:  chrome_navigate(staging) → chrome_click(uid:el-add-to-cart) → chrome_screenshot(./repro/01-cart.png)
         → chrome_click(uid:el-checkout) → chrome_list_network_requests() → chrome_screenshot(./repro/02-500.png)
         ✓ POST /api/checkout → 500. Response body saved → ./repro/checkout-500.json
@@ -112,13 +111,13 @@ You:    [files the ticket with the folder attached]
 > Snapshot `localhost:3000` and the staging URL of the same page; tell me what's visually different.
 
 **Auth-only data pull**
-> Open my analytics dashboard tab and `chrome_evaluate` to extract today's KPIs from page state.
+> Open my analytics dashboard tab and pull today's KPIs from the page.
 
 **Network forensics**
-> Reproduce the checkout bug, then use `chrome_list_network_requests` to find the failing call and dump its response body.
+> Reproduce the checkout bug, find the failing API call, and dump its response body.
 
 **File upload through React**
-> Open the photo uploader, `chrome_upload_file` with `./fixtures/sample.png`, confirm preview rendered.
+> Open the photo uploader, upload `./fixtures/sample.png`, confirm the preview renders.
 
 </details>
 
diff --git a/extensions/chrome-profile-bridge/browser-extension/manifest.json b/extensions/chrome-profile-bridge/browser-extension/manifest.json
index 53f5418..d998d19 100644
--- a/extensions/chrome-profile-bridge/browser-extension/manifest.json
+++ b/extensions/chrome-profile-bridge/browser-extension/manifest.json
@@ -1,7 +1,7 @@
 {
   "manifest_version": 3,
   "name": "Pi Chrome Connector",
-  "version": "0.15.0",
+  "version": "0.15.1",
   "description": "Lets Pi control tabs in Chrome via a local connector at 127.0.0.1.",
   "permissions": [
     "tabs",
diff --git a/package.json b/package.json
index 5a52542..37935a6 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "pi-chrome",
-	"version": "0.15.1",
+	"version": "0.15.2",
 	"scripts": {
 		"version": "node scripts/sync-manifest-version.js",
 		"prepublishOnly": "node scripts/sync-manifest-version.js"