visual-companionlisted

# Visual Companion Browser-based visual companion for rendering mockups, diagrams, and interactive options. The server watches a directory for HTML files and serves the newest one to the browser. You write HTML content, the user sees it in their browser and can click to select options. ## When to Use Decide per-question, not per-session. The test: **would the user understand this better by seeing it than reading it?** **Use the browser** when the content itself is visual: - **UI mockups** -- wireframes, layouts, navigation structures, component designs - **Architecture diagrams** -- system components, data flow, relationship maps - **Side-by-side visual comparisons** -- comparing two layouts, two color schemes, two design directions - **Design polish** -- when the question is about look and feel, spacing, visual hierarchy - **Spatial relationships** -- state machines, flowcharts, entity relationships rendered as diagrams **Use the terminal** when the content is text or tabular: - **Requirements and scope questions** -- "what does X mean?", "which features are in scope?" - **Conceptual A/B/C choices** -- picking between approaches described in words - **Tradeoff lists** -- pros/cons, comparison tables - **Technical decisions** -- API design, data modeling, architectural approach selection - **Clarifying questions** -- anything where the answer is words, not a visual preference A question _about_ a UI topic is not automatically a visual question. "What kind of wizard do