Visual Concept

visual-concept (映)

Transform technical conversations and insights into visual concept guides. Creates conceptual inspiration for music videos or visual content — symbolic imagery, color palette evolution, and thematic direction without prescriptive shot lists.

Trigger: 明示呼出 (explicit invocation) or when deep technical insight emerges

Core insight: "Visual metaphors make abstract concepts tangible. The right image can convey what words cannot."

Installation

openclaw install leegitw/visual-concept

Dependencies: None (standalone creative skill)

Data handling: This skill synthesizes content from user-supplied input or the current conversation context (default). It does NOT read files from the workspace or access project artifacts directly. Results are returned to the invoking agent, who decides how to use them.

What This Solves

Technical concepts are abstract. Visual representation makes them memorable and shareable. This skill:

1. Translates technical concepts into visual metaphors 2. Creates color arcs that match emotional journeys 3. Provides creative direction without constraining execution

The insight: A well-chosen visual metaphor (trace IDs as golden threads, errors as cracks in glass) communicates instantly what paragraphs cannot.

Usage

/vc [topic]

Arguments

| Argument | Required | Description | |----------|----------|-------------| | topic | No | Topic focus (default: synthesize current conversation) |

Pre-Requisites

Before creating a visual concept, ensure:

1. Sufficient conversation depth — Surface-level topics don't inspire visuals 2. Clear narrative arc — Problem → Discovery → Solution → Impact 3. Main work documented — Save current progress first if mid-task

Context Understanding Checklist

You must be able to answer:

| Question | What It Means | |----------|---------------| | Core insight? | Not "we talked about X" but "we discovered X solves Y" | | Problem solved? | The pain point, not just the topic | | Why, not just what? | The reasoning, not just the outcome | | Visual potential? | Can this be represented symbolically? |

Red Flags (Don't Create)

Output Format

Visual Concept Guide Structure

## Visual Concept Guide
Core Visual Concept: [Primary metaphor in one sentence]
Visual Themes & Imagery
[3-7 major themes, conceptual not prescriptive]
Symbolic Visual Elements
[How technical concepts become visual symbols]
Emotional Color Arc
[Color palette evolution matching emotional journey]
Typography & Text Elements
[If applicable, style of any on-screen text]
Motion & Rhythm
[Movement patterns, pacing notes]
Key Visual Contrasts
[Before/after, chaos/order, dark/light]

Visual Guide Rules

| Rule | Description | |------|-------------| | Conceptual inspiration | NOT a shot list or scene breakdown | | NO specific durations | Don't say "5 seconds on X" | | NO camera angles | Don't prescribe "wide shot" or "close-up" | | NO literal breakdown | Don't number scenes sequentially | | Provide direction | Give creative directors a north star, not constraints |

Example: Good vs Bad

Bad (too prescriptive):

Scene 1 (0:00-0:05): Wide shot of server room, camera slowly zooms in
Scene 2 (0:05-0:10): Close-up of blinking lights, pan left to right

Good (conceptual):

Core Visual Concept: Darkness giving way to illumination
Visual Themes:
Isolation in darkness (before observability)
Golden threads appearing (trace IDs connecting)
Gradual dawn (understanding emerging)
Color Arc:
Opens in deep blues and blacks
Warm gold appears as connections form
Ends in clear, bright tones

Core Logic

Step 1: Synthesize Conversation

Step 2: Identify Narrative Arc

| Element | Question | |---------|----------| | Problem | What was broken/painful? | | Discovery | What did we learn? | | Solution | What pattern emerged? | | Impact | Why does this matter? |

Step 3: Find Visual Metaphors

Think about:

Step 4: Write Concept Guide

Include:

Example

Input: Bootstrap Observability Insight

Context: Discovered reproduce-to-debug problem. Introduced Bootstrap → Learn → Enforce phases.

Narrative arc:

Output

Core Visual Concept: From blindness to sight — darkness giving way to illuminated pathways

Visual Themes & Imagery

1. The Void — Empty black space representing systems without observability 2. Scattered Sparks — Data points appearing, unconnected 3. Golden Threads — Trace IDs weaving connections between sparks 4. The Pattern Emerges — Threads form a recognizable structure 5. Dawn Breaking — Full illumination, the system becomes visible 6. The Watchtower — Elevated view of the now-visible landscape

Symbolic Visual Elements

| Concept | Visual Symbol | |---------|---------------| | Trace IDs | Golden threads connecting points | | Errors | Red fractures or cracks | | Baselines | Horizontal reference lines, like horizon | | Bootstrap phase | Seeds planted, construction scaffolding | | Enforcement | Solid walls, protective barriers |

Emotional Color Arc

Motion & Rhythm

Key Visual Contrasts

| Before | After | |--------|-------| | Darkness | Light | | Scattered | Connected | | Chaos | Pattern | | Blindness | Vision | | Isolation | Network |

Integration

Failure Modes

| Condition | Behavior | |-----------|----------| | Insufficient context | Ask clarifying questions first | | No clear narrative arc | Decline, explain what's missing | | Purely procedural insight | Suggest finding visual angle first |

Security Considerations

Input sources:

What this skill does NOT do:

Output behavior: This skill returns the visual concept guide directly to the invoking agent. The agent can then display, save, or pass the result to another skill as needed.

Provenance note: This skill is developed by Live Neon (https://github.com/live-neon/skills) and published to ClawHub under the leegitw account. Both refer to the same maintainer.

Quality Checklist

Acceptance Criteria

*Part of the Live Neon Creative Suite.*