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: 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

ArgumentRequiredDescriptiontopicNoTopic 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: QuestionWhat It MeansCore insight?Not "we talked about X" but "we discovered X solves Y"Problem solved?The pain point, not just the topicWhy, not just what?The reasoning, not just the outcomeVisual potential?Can this be represented symbolically?

Red Flags (Don't Create)

Surface-level summary of conversation Don't understand why a decision was made Insight is purely procedural with no visual metaphor No clear emotional arc to visualize

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

RuleDescriptionConceptual inspirationNOT a shot list or scene breakdownNO specific durationsDon't say "5 seconds on X"NO camera anglesDon't prescribe "wide shot" or "close-up"NO literal breakdownDon't number scenes sequentiallyProvide directionGive 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

Step 1: Synthesize Conversation

Read full conversation context Identify key decisions, "aha" moments Extract core insight or pattern

Step 2: Identify Narrative Arc

ElementQuestionProblemWhat was broken/painful?DiscoveryWhat did we learn?SolutionWhat pattern emerged?ImpactWhy does this matter?

Step 3: Find Visual Metaphors

Think about: What does the problem LOOK like? (chaos, darkness, fragmentation) What does the solution LOOK like? (order, light, connection) What symbols represent the key concepts? What color palette matches the emotional journey?

Step 4: Write Concept Guide

Include: Core visual concept (one sentence) 3-7 visual themes Symbolic elements for technical concepts Color arc (start → middle → end) Motion and rhythm notes Key contrasts

Input: Bootstrap Observability Insight

Context: Discovered reproduce-to-debug problem. Introduced Bootstrap → Learn → Enforce phases. Narrative arc: Problem: Debugging without reproduction is impossible Discovery: Greenfield systems don't know what "normal" is Solution: Bootstrap → Learn → Enforce phases Impact: Debug with sight instead of in darkness

Output

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

Visual Themes & Imagery

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

Symbolic Visual Elements

ConceptVisual SymbolTrace IDsGolden threads connecting pointsErrorsRed fractures or cracksBaselinesHorizontal reference lines, like horizonBootstrap phaseSeeds planted, construction scaffoldingEnforcementSolid walls, protective barriers

Emotional Color Arc

Opening: Deep blues, blacks — isolation, confusion Middle: Warm golds emerging — discovery, connection Climax: Bright whites and golds — clarity, understanding Resolution: Balanced palette — sustainable, calm confidence

Motion & Rhythm

Opens slow, contemplative (lost in darkness) Accelerates with discovery (threads appearing rapidly) Peaks with revelation (burst of light) Settles into steady rhythm (system functioning)

Key Visual Contrasts

BeforeAfterDarknessLightScatteredConnectedChaosPatternBlindnessVisionIsolationNetwork

Integration

Layer: Creative Depends on: None (standalone) Used by: side-quests (combo skill) Complements: insight-song, ted-talk

Failure Modes

ConditionBehaviorInsufficient contextAsk clarifying questions firstNo clear narrative arcDecline, explain what's missingPurely procedural insightSuggest finding visual angle first

Security Considerations

Input sources: User-supplied context (if provided) Current conversation context (default) What this skill does NOT do: Read files from the workspace Access project artifacts directly Send data to external services Call image generation APIs 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

Can explain core insight in one sentence Core visual concept is clear and evocative 3-7 visual themes identified Technical concepts have symbolic representations Color arc matches emotional journey NO prescriptive shot lists or durations Could guide a creative director without constraining them

Acceptance Criteria

/vc synthesizes input or conversation into visual concept guide Output includes core concept, themes, symbols, color arc Guide is inspirational, not prescriptive Technical concepts translated to visual metaphors Result returned to invoking agent Part of the Live Neon Creative Suite.