Writes Godot 4 shaders: Godot Shading Language, VisualShader, CanvasItem and Spatial shaders, post-processing. Use when authoring a Godot shader or profiling shader cost on a target device.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add poorvith-mp/skills-gamedev --skill godot-shader-developer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Godot Shader Developer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/poorvith-mp-godot-shader-developer)More formats (shields.io, HTML) on the badges page.
---
name: godot-shader-developer
description: >-
Writes Godot 4 shaders: Godot Shading Language, VisualShader, CanvasItem and Spatial shaders,
post-processing. Use when authoring a Godot shader or profiling shader cost on a target device.
---
# Godot Shader Developer
## Core Mission
- 2D CanvasItem shaders for sprite effects, UI polish, 2D post-processing
- 3D Spatial shaders for surface materials, world effects, volumetrics
- VisualShader graphs for artist-accessible material variation
- CompositorEffect for full-screen post-processing
- Profile with Godot's built-in rendering profiler
## Critical Rules
- Godot shading language is not raw GLSL — use Godot built-ins (TEXTURE, UV, COLOR)
- Declare shader_type at top: canvas_item, spatial, particles, or sky
- Target correct renderer: Forward+, Mobile, or Compatibility
- Avoid SCREEN_TEXTURE sampling in tight loops on mobile
- All uniforms need hints (hint_range, source_color, etc.)
## Success Metrics
- All shaders declare shader_type and document renderer requirements
- All uniforms have appropriate hints
- Mobile-targeted shaders pass Compatibility mode
- No SCREEN_TEXTURE without documented performance justification
## Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Godot Shader Developer workflow; avoid generic filler.
## Verification & Quality Checklist
- [ ] Code compiles and all automated tests and typechecks pass without new warnings.
- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
- [ ] Changes are covered by a test that fails without them.
## Anti-Patterns & Constraints
- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.
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!