Skip to content
Back to skills

Shader

ASecurity

Reviews Godot Shader/Material implementation for known pitfalls. Triggers AFTER implementation, when code involves ShaderMaterial, set_shader_parameter, .gdshader, VisualShader, hint_screen_texture, BackBufferCopy, instance uniform, or uniform declarations. Do NOT use this skill for planning or teaching — only for post-implementation review.

  • 547 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 11, 2026
developmentgonodeapi

Works with

  • api

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned June 11, 2026

npx -y skills add RandallLiuXin/GodotMaker --skill shader --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Shader?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Shader
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/randallliuxin-shader/badge)](https://www.skillsdirectory.com/skills/randallliuxin-shader)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: shader-review
description: |
  Reviews Godot Shader/Material implementation for known pitfalls.
  Triggers AFTER implementation, when code involves ShaderMaterial,
  set_shader_parameter, .gdshader, VisualShader, hint_screen_texture,
  BackBufferCopy, instance uniform, or uniform declarations.
  Do NOT use this skill for planning or teaching — only for post-implementation review.
---

# Shader Review

Post-implementation reviewer for Godot shader code. Checks against known gotchas that LLMs consistently get wrong.

## When to trigger

After shader-related code is written or modified. Look for:
- ShaderMaterial, `.gdshader` files, VisualShader resources
- `set_shader_parameter()` / `SetShaderParameter()` calls
- `hint_screen_texture`, BackBufferCopy nodes
- `instance uniform` declarations
- Uniform type assignments in scripts

## Review process

1. Read `gotchas.md`
2. Scan the implemented code against each gotcha
3. For each hit:
   - Cite the gotcha ID (e.g. G1)
   - Show the offending code
   - Provide the fix
4. If no hits, report clean
5. Optionally run `checklist.md` static checks for automated verification

When you need specific API details, delegate to the **godot-api** skill.

Files in this skill

  • SKILL.md1.2 KB
  • checklist.md2.2 KB
  • gotchas.md4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…