diff --git a/skills/brainstorming/scripts/frame-template.html b/skills/brainstorming/scripts/frame-template.html index dcfe0181..6325ef91 100644 --- a/skills/brainstorming/scripts/frame-template.html +++ b/skills/brainstorming/scripts/frame-template.html @@ -13,7 +13,7 @@ * - Scrollable main content area * - CSS helpers for common UI patterns * - * Content is injected via placeholder comment in #claude-content. + * Content is injected via placeholder comment in #frame-content. */ * { box-sizing: border-box; margin: 0; padding: 0; } @@ -77,7 +77,7 @@ .header .status::before { content: ''; width: 6px; height: 6px; background: var(--success); border-radius: 50%; } .main { flex: 1; overflow-y: auto; } - #claude-content { padding: 2rem; min-height: 100%; } + #frame-content { padding: 2rem; min-height: 100%; } .indicator-bar { background: var(--bg-secondary); @@ -201,7 +201,7 @@
-
+
diff --git a/skills/brainstorming/visual-companion.md b/skills/brainstorming/visual-companion.md index 2113863d..4b4d9db7 100644 --- a/skills/brainstorming/visual-companion.md +++ b/skills/brainstorming/visual-companion.md @@ -49,20 +49,13 @@ Save `screen_dir` and `state_dir` from the response. Tell user to open the URL. **Launching the server by platform:** -**Claude Code (macOS / Linux):** +**Claude Code:** ```bash -# Default mode works — the script backgrounds the server itself +# Default mode works — the script backgrounds the server itself. scripts/start-server.sh --project-dir /path/to/project ``` -**Claude Code (Windows):** -```bash -# Windows auto-detects and uses foreground mode, which blocks the tool call. -# Use run_in_background: true on the Bash tool call so the server survives -# across conversation turns. -scripts/start-server.sh --project-dir /path/to/project -``` -When calling this via the Bash tool, set `run_in_background: true`. Then read `$STATE_DIR/server-info` on the next turn to get the URL and port. +On Windows, the script auto-detects and switches to foreground mode (which blocks the tool call). Use `run_in_background: true` on the Bash tool call so the server survives across conversation turns, then read `$STATE_DIR/server-info` on the next turn to get the URL and port. **Codex:** ```bash @@ -78,6 +71,14 @@ scripts/start-server.sh --project-dir /path/to/project scripts/start-server.sh --project-dir /path/to/project --foreground ``` +**Copilot CLI:** +```bash +# Use --foreground and start the server via the bash tool with mode: "async" +# so the process survives across turns. Capture the returned shellId for +# read_bash / stop_bash if you need to interact with it later. +scripts/start-server.sh --project-dir /path/to/project --foreground +``` + **Other environments:** The server must keep running in the background across conversation turns. If your environment reaps detached processes, use `--foreground` and launch the command with your platform's background execution mechanism. If the URL is unreachable from your browser (common in remote/containerized setups), bind a non-loopback host: @@ -97,7 +98,7 @@ Use `--url-host` to control what hostname is printed in the returned URL JSON. - Before each write, check that `$STATE_DIR/server-info` exists. If it doesn't (or `$STATE_DIR/server-stopped` exists), the server has shut down — restart it with `start-server.sh` before continuing. The server auto-exits after 30 minutes of inactivity. - Use semantic filenames: `platform.html`, `visual-style.html`, `layout.html` - **Never reuse filenames** — each screen gets a fresh file - - Use Write tool — **never use cat/heredoc** (dumps noise into terminal) + - Use your file-creation tool — **never use cat/heredoc** (dumps noise into terminal) - Server automatically serves the newest file 2. **Tell user what to expect and end your turn:** diff --git a/skills/executing-plans/SKILL.md b/skills/executing-plans/SKILL.md index a5918627..78d88540 100644 --- a/skills/executing-plans/SKILL.md +++ b/skills/executing-plans/SKILL.md @@ -11,7 +11,7 @@ Load plan, review critically, execute all tasks, report when complete. **Announce at start:** "I'm using the executing-plans skill to implement this plan." -**Note:** Tell your human partner that Superpowers works much better with access to subagents. The quality of its work will be significantly higher if run on a platform with subagent support (such as Claude Code or Codex). If subagents are available, use superpowers:subagent-driven-development instead of this skill. +**Note:** Tell your human partner that Superpowers works much better with access to subagents. The quality of its work will be significantly higher if run on a platform with subagent support (Claude Code, Codex CLI, Codex App, Copilot CLI, and Gemini CLI all qualify; see the per-platform tool refs in `../using-superpowers/references/`). If subagents are available, use superpowers:subagent-driven-development instead of this skill. ## The Process @@ -19,7 +19,7 @@ Load plan, review critically, execute all tasks, report when complete. 1. Read plan file 2. Review critically - identify any questions or concerns about the plan 3. If concerns: Raise them with your human partner before starting -4. If no concerns: Create TodoWrite and proceed +4. If no concerns: Create todos for the plan items and proceed ### Step 2: Execute Tasks diff --git a/tests/brainstorm-server/server.test.js b/tests/brainstorm-server/server.test.js index 4797cbb9..2cccf095 100644 --- a/tests/brainstorm-server/server.test.js +++ b/tests/brainstorm-server/server.test.js @@ -406,7 +406,7 @@ async function runTests() { assert(template.includes('indicator-bar'), 'Should have indicator bar'); assert(template.includes('indicator-text'), 'Should have indicator text'); assert(template.includes(''), 'Should have content placeholder'); - assert(template.includes('claude-content'), 'Should have content container'); + assert(template.includes('frame-content'), 'Should have content container'); return Promise.resolve(); });