Shader performance optimization skill for instruction counting, GPU profiling, and rendering efficiency.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill shader-optimization --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Shader Optimization?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-shader-optimization-babysitter)More formats (shields.io, HTML) on the badges page.
---
name: shader-optimization
description: Shader performance optimization skill for instruction counting, GPU profiling, and rendering efficiency.
allowed-tools: Read, Grep, Write, Bash, Edit, Glob, WebFetch
graph:
domains: [domain:gaming]
specializations: [specialization:game-development]
skillAreas: [skill-area:shader-programming, skill-area:performance-monitoring-profiling]
roles: [role:game-developer]
---
# Shader Optimization Skill
Shader performance optimization techniques.
## Overview
This skill provides capabilities for optimizing shader performance.
## Capabilities
- Instruction counting
- ALU optimization
- Texture sample reduction
- Shader variant management
- GPU profiling
## Best Practices
1. Minimize texture samples
2. Use half precision where possible
3. Avoid branching
4. Batch similar shaders
5. Profile on target hardware
## References
- Engine-specific profiling tools
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...