| name | visual-concept |
| version | 1.0.1 |
| description | Transform technical insights into visual concept guides — symbolic imagery, color arcs, and creative direction for video |
| author | Live Neon <hello@liveneon.ai> |
| homepage | https://github.com/live-neon/skills/tree/main/creative/visual-concept |
| repository | leegitw/visual-concept |
| license | MIT |
| tags | ["creative","visual","video","concept-art","storyboard","direction","synthesis","reflection","imagery"] |
| layer | creative |
| status | active |
| alias | vc |
| user-invocable | true |
| emoji | 🎬 |
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:
- Translates technical concepts into visual metaphors
- Creates color arcs that match emotional journeys
- 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:
- Sufficient conversation depth — Surface-level topics don't inspire visuals
- Clear narrative arc — Problem → Discovery → Solution → Impact
- 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? |
