| name | brainstorm-visual-companion |
| description | How to start the brainstorming visual companion server on Windows and use it for UI brainstorming sessions. |
| source | auto-skill |
| extracted_at | 2026-06-14T09:27:25.957Z |
Brainstorming Visual Companion on Windows
Starting the Server
The start-server.sh script doesn't work directly from cmd.exe. Use this approach:
- Create the session directories:
mkdir C:\Dev\Titan\.superpowers\brainstorm\visual-session\state
mkdir C:\Dev\Titan\.superpowers\brainstorm\visual-session\content
- Start the server directly via node:
set "BRAINSTORM_DIR=C:\Dev\Titan\.superpowers\brainstorm\visual-session" & set "BRAINSTORM_HOST=127.0.0.1" & set "BRAINSTORM_URL_HOST=localhost" & set "BRAINSTORM_OWNER_PID=0" & node C:\Users\emper\.qwen\skills\brainstorming\scripts\server.cjs
Critical gotchas:
- Use
set "KEY=VALUE" with quotes — no trailing spaces! Trailing spaces become part of the value and cause ENOTFOUND DNS errors.
- Chain with
& not && so all env vars are set before node starts.
- Run in a background shell (
is_background: true).
- Read the output file to get the server URL and port.
- The server outputs a JSON line:
{"type":"server-started","port":58309,"host":"127.0.0.1","url_host":"localhost","url":"http://localhost:58309","screen_dir":"...","state_dir":"..."}
- Write the server-info file so the event loop works:
{same JSON as above}
Using the Companion
- Write HTML content fragments (no
<!DOCTYPE> needed) to $screen_dir/<name>.html
- The server serves the newest file by modification time
- Click events are recorded to
$state_dir/events as JSONL
- When switching to non-visual questions, push a waiting screen to clear stale content
When to Use
- UI mockups — wireframes, layouts, navigation structures
- Architecture diagrams — system components, data flow
- Side-by-side comparisons — two layouts, color schemes, design directions
- Design polish — spacing, visual hierarchy questions
When NOT to Use
- Requirements and scope questions
- Conceptual A/B/C choices
- Tradeoff lists
- Technical decisions (API design, data modeling)