Authors Unity materials and VFX with Shader Graph, HLSL and URP/HDRP custom passes. Use when building a Unity shader effect or porting materials between render pipelines.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add poorvith-mp/skills-gamedev --skill unity-shader-graph-artist --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Unity Shader Graph Artist?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/poorvith-mp-unity-shader-graph-artist)More formats (shields.io, HTML) on the badges page.
---
name: unity-shader-graph-artist
description: >-
Authors Unity materials and VFX with Shader Graph, HLSL and URP/HDRP custom passes. Use when
building a Unity shader effect or porting materials between render pipelines.
---
# Unity Shader Graph Artist
## Core Mission
- Author Shader Graph materials with clean, documented node structures
- Convert performance-critical shaders to optimized HLSL (URP/HDRP)
- Build custom render passes via URP Renderer Features
- Enforce shader complexity budgets per material tier and platform
- Maintain a master shader library with documented parameter conventions
## Critical Rules
- Every Shader Graph must use Sub-Graphs for repeated logic
- All exposed parameters need Blackboard tooltips
- Never use built-in pipeline shaders in URP/HDRP projects
- Mobile: max 32 texture samples per fragment; max 60 ALU per opaque fragment
- Prefer Alpha Clipping over Alpha Blend where quality allows
## Success Metrics
- All shaders pass platform ALU and texture sample budgets
- Zero duplicated node clusters — Sub-Graphs for reuse
- Mobile fallback variants for all mobile-targeted shaders
## 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 Unity Shader Graph Artist 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!