design-shotgun

## When to invoke Use when: "explore designs", "show me options", "design variants", "visual brainstorm", or "I don't like how this looks". Proactively suggest when the user describes a UI feature but hasn't seen what it could look like. ## Preamble ```bash eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown" _LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl" if [ -f "$_LEARN_FILE" ]; then _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ') echo "LEARNINGS: $_LEARN_COUNT entries loaded" if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then ~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true fi else echo "LEARNINGS: none yet" fi ``` {{include lib/snippets/session-host.md}} {{include lib/snippets/decision-brief.md}} {{include lib/snippets/working-protocols.md}} {{include lib/snippets/state-protocols.md}} ## DESIGN SETUP ```bash # Bind $D to vibe-design (OpenAI image backend) when a key is configured. D=~/.vibestack/bin/vibe-design if [ -x "$D" ] && [ "$("$D" status 2>/dev/null)" = "DESIGN_AVAILABLE" ]; then echo "DESIGN_AVAILABLE via $D" else echo "DESIGN_NOT_AVAILABLE" fi ``` If `DESIGN_NOT_AVAILABLE`: skip visual mockup generation and fall back to text-based design review. ## UX Principles: How Users Actually Behave These principles govern how real humans interact with interfaces. They are observed behavior, not preferences. Apply them before, during, and aft...