Art Vision | creative-direction | ClaudePluginHub

Skill

Community

Art Vision

From creative-direction

1

Description

This skill should be used when the user asks about "art direction", "visual style", "color palette", "aesthetic", "visual coherence", "art style guide", "visual identity", "character design style", "environment style", "UI style", or discusses establishing or reviewing visual direction. Provides art direction framework for visual coherence.

Install

1

Add the repository(one-time)

$

/plugin marketplace add nethercore-systems/nethercore-ai-plugins

2

Install the plugin

$

/plugin install creative-direction@nethercore-ai-plugins

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Supporting Assets

View in Repository

references/color-theory.md

references/composition.md

references/style-spectrums.md

Skill Content

Art Vision

Establish and maintain visual coherence through systematic art direction.

Visual Hierarchy

Three levels every scene communicates through:

Primary Focus - Player's eye (characters, interactives)
Secondary Context - Navigation, environmental storytelling
Tertiary Atmosphere - Background, mood reinforcement

Style Spectrum Positioning

Spectrum	Left ←→ Right
Fidelity	Stylized ←→ Realistic
Detail	Simplified ←→ Complex
Saturation	Desaturated ←→ Vibrant
Contrast	Low-key ←→ High-key
Form	Geometric ←→ Organic
Line	Hard-edge ←→ Painterly

Document position for each. All assets should align.

Color Theory

Primary Palette (60/30/10 rule):

Dominant (60%): Sets tone
Secondary (30%): Creates interest
Accent (10%): Draws attention

Functional Colors:

Player/friendly: Consistent hue
Enemy/danger: Distinct, high recognition
Interactive: Subtle affordance cue
UI: Readable on all backgrounds

Emotional Mapping:

Safe zones: Warmer, saturated
Danger zones: Cooler, desaturated, high contrast

Style Bible Sections

Visual Pillars - 3-5 non-negotiable style principles
Reference Board - Target aesthetic by category
Color Keys - Paintings for major environments/moods
Material Definitions - Surface treatments, normal map intensity
Character Design Language - Proportions, silhouettes
Environment Design Language - Scale, architecture

Normal Map Aesthetic Guidelines

Normal maps add surface detail. Use consistently with visual style:

Style	Normal Map Intensity	Recommendation
Stylized/Toon	0.3-0.5	Subtle or skip
PS1/N64 Retro	0.5-0.8	Subtle detail
PS2/Dreamcast	0.8-1.2	Standard detail
Realistic	1.0-2.0	Full detail

When to use normal maps:

Hero characters requiring close-up detail
Architecture with visible surface texture
Materials that rely on micro-detail (metal, fabric, stone)

When to skip normal maps:

Flat-shaded stylized aesthetics
Memory-constrained scenarios
Distant or fast-moving objects
When geometry provides sufficient form

Material-specific intensity:

Material	Intensity Range
Smooth plastic	0.2-0.4
Fabric/cloth	0.5-0.8
Stone/concrete	0.8-1.2
Metal (brushed)	1.0-1.5
Organic (bark, skin)	0.6-1.0

Coherence Checklist

Fidelity matches other assets?
Detail density appropriate for hierarchy role?
Palette used correctly?
Shape language consistent?
Integrates with intended environment?

Store in .studio/art-direction.md or .studio/creative-direction.md.

References

references/color-theory.md - Advanced palette building
references/composition.md - Visual hierarchy principles
references/style-spectrums.md - Detailed spectrum definitions

Links

GitHub Stats

0 forks

Updated 4 days ago

Similar Skills

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

53.4k

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

53.4k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

53.4k