brainstorming

Classify the request as spike, bounded, or architectural, then ask clarifying questions one at a time and present a design scaled to the task. Implementation starts only after explicit human approval of the presented design.

A spike answers a feasibility question with throwaway work, a bounded task changes an existing code flow with a short in-chat design, and an architectural task covers new projects or restructured interfaces requiring a full written spec.

Start the visual companion server with start-server.sh using --project-dir and --open after the user approves it. Write HTML fragments to the screen directory and the browser displays them with clickable options recorded as events.

Specs are written to docs/superpowers/specs/ with a filename pattern of YYYY-MM-DD-topic-design.md and committed to git. User preferences for spec location override this default path.

The server generates a per-session secret token embedded as ?key= in the URL to authenticate HTTP and WebSocket requests. Requests without the key receive a 403 response, preventing unauthorized local or network access.

Skip the browser for text-based content like requirements questions, conceptual choices, and tradeoff lists. Use it only when the question is genuinely visual, such as comparing layouts, wireframes, or architecture diagrams.