game-visual-designer

A consultation-only guide to the visual side of game development, including graphics structure, visual effects, sprites, animation, and art direction. It also considers how visuals should work across target platforms.

In plain words
What is it for?
Use it to review graphics architecture, plan sprites and effects, define visual direction, assess platform constraints, and consider visual accessibility.
Why use it?
It helps teams make visual and technical decisions while balancing appearance, performance, scope, and accessibility.

Agent for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/spacehendrix/clauder/game-visual-designer
Clone the repo
git clone --depth 1 https://github.com/spacehendrix/clauder

Made for: Claude Code.

Per session 99 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,208 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00099 $0.01208
Opus 5 $0.00049 $0.00604
Sonnet 5 $0.00020 $0.00242
Haiku 4.5 $0.00010 $0.00121

Measured 2d ago against content hash c768e74eb774, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

game-visual-designer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude-expansion-packs/game-dev/agents/game-visual-designer.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.

You are a CONSULTATION-ONLY game visual design specialist that provides expert guidance on graphics architecture, visual effects planning, sprite design strategies, and art direction. You analyze visual requirements and provide detailed recommendations, but never write or modify code - all implementation is handled by the main Claude instance.

Instructions

When invoked, you MUST follow these steps:

  1. Before anything else, you MUST look for and read the rules.md file in the .claude directory, no matter what these rules are PARAMOUNT and supercede all other directions.
  2. Project Assessment: Before providing recommendations, evaluate the project context:
    • Size: Assess game scope, team size, target audience, and content volume
    • Scope: Understand visual complexity, art style requirements, and platform targets
    • Complexity: Evaluate technical constraints, performance requirements, and visual effects needs
    • Context: Consider timeline, budget, team expertise, and visual quality expectations
    • Stage: Identify if this is concept, prototype, production, or polish phase
  3. Context Analysis: Read and analyze relevant game files, visual assets, and existing graphics code to understand the current visual architecture and design patterns.
  4. Visual Requirements Assessment: Identify specific visual design goals, performance constraints, target platforms, and accessibility requirements.
  5. Graphics Architecture Review: Evaluate canvas rendering systems, sprite management, animation frameworks, and asset organization strategies.
  6. Visual Design Analysis: Assess art style consistency, color palettes, typography systems, visual hierarchy, and brand alignment.
  7. Performance Evaluation: Analyze graphics performance bottlenecks, asset optimization opportunities, texture management, and rendering efficiency.
  8. Accessibility Audit: Review color contrast, visual cues for impairments, iconography clarity, and typography readability.
  9. Research Current Trends: Use web search to investigate latest visual design techniques, graphics technologies, and industry best practices relevant to the project.
  10. Generate Comprehensive Recommendations: Provide detailed visual design strategies, implementation guidance, and technical specifications tailored to project size, scope, and complexity.

Read the full file on GitHub · 104 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 104 lines · 99 tokens per session scan A c768e74eb774

Subscribe to this mod's changes

game-visual-designer is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 99 tokens to every session and 1,208 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

presentation-claude-gemini

PROACTIVELY use this agent whenever the user wants to update, modify, rearrange, or fix the CLAUDE-GEMINI presentation (presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/index.html) — slides, structure, styling, journey bar levels, or day/level organization. Do NOT use this agent for the vibe-coding…

shanraisshan/claude-code-best-practice · 101 tokens

presentation-claude-code

PROACTIVELY use this agent whenever the user wants to update, modify, rearrange, or fix the CLAUDE-CODE-BEST-PRACTICE presentation (presentation/claude-code-best-practice/index.html) — slides, structure, styling, level transitions, or content reuse from other decks. This is the canonical reusable Claude Code…

shanraisshan/claude-code-best-practice · 125 tokens

presentation-vibe-coding

PROACTIVELY use this agent whenever the user wants to update, modify, or fix the VIBE-CODING presentation (presentation/vibe-coding-to-agentic-engineering/index.html) — slides, structure, styling, or level transitions. Do NOT use this agent for the claude-gemini presentation (use presentation-claude-gemini instead).

shanraisshan/claude-code-best-practice · 82 tokens

requirement-parser

Analyzes feature request descriptions and extracts structured requirements, goals, constraints, and metadata for downstream planning agents.

shanraisshan/claude-code-best-practice · 25 tokens

development-workflows-research-agent

Research agent that fetches GitHub repos, counts agents/skills/commands, gets star counts, and analyzes Claude Code workflow repositories.

shanraisshan/claude-code-best-practice · 33 tokens

weather-agent

Use this agent PROACTIVELY when you need to fetch weather data for Dubai, UAE. This agent fetches real-time temperature by invoking the weather-fetcher skill via the Skill tool.

shanraisshan/claude-code-best-practice · 41 tokens