From b23d02fd955369e5d968f9414b9448b660912296 Mon Sep 17 00:00:00 2001
From: fredericrous <frederic.rousseau.fr@gmail.com>
Date: Sat, 24 Oct 2026 23:32:16 +0200
Subject: [PATCH] docs(preview): source the default-browser step

The deployed skill carried decisions#83's edit; the chezmoi source
did not, so an apply would have erased it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 dot_claude/skills/worktree-task/SKILL.md | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/dot_claude/skills/worktree-task/SKILL.md b/dot_claude/skills/worktree-task/SKILL.md
index 02024f9..6a516bd 100644
--- a/dot_claude/skills/worktree-task/SKILL.md
+++ b/dot_claude/skills/worktree-task/SKILL.md
@@ -312,9 +312,15 @@ below names one of them.
      Its JSON prints `question_prefix` (`[preview <id>] <label>`): the
      question in step 6 starts with it, verbatim. A register that did not
      bind says so right after it runs; run the command it prints.
-  5. **Open the app for them** with Claude in Chrome: a tab at the URL,
-     already at the state step 1 of "Try it" reaches (for example the panel
-     already open). Say which tab it is.
+  5. **Open the app for them in their default browser**: `open '<url>'`
+     (macOS opener), with the URL deep-linked to the state step 1 of "Try
+     it" reaches where a route or query can carry it. Never open the
+     person's page with chrome-devtools MCP, Playwright or any headless or
+     automation Chrome: that window is the agent's, it lives in a separate
+     profile and the person does not see it, or sees it as a stray window.
+     Those tools are for the agent's own checks only. When the state needs
+     clicks a URL cannot carry, open the URL and let step 1 of "Try it" say
+     the click. Say what was opened.
   6. **Print the brief in the terminal**: the guide's sections, short. Then,
      in the SAME turn, ask ONE marked question with AskUserQuestion:
      - its text begins with the register's `question_prefix`, verbatim,