---
name: visual-brainstorm-companion
description: Use during brainstorm only when the problem is strongly visual (complex UI, flow mapping, alternatives) and create optional browser/canvas artifacts.
---

# Visual Brainstorm Companion

Use this skill only when visual output materially improves decision quality.

## Trigger examples

- Multi-step UI flow where layout affects behavior
- Comparing 2-3 design alternatives with trade-offs
- Data flow that is hard to understand in text

## Do not use for

- Pure backend architecture decisions
- Small bugfix discussions
- Text-only requirement clarification

## Flow

1. Confirm visual aid is useful for this brainstorm.
2. Create one focused visual artifact (diagram/mockup), not many.
3. Summarize decisions derived from the visual in the brainstorm doc.
4. Keep visual step optional and token-conscious.