Unity Shader Skills

Overview

Work with shaders - create shader files, read source code, and list available shaders.

Common Mistakes

DO NOT (common hallucinations):

• shader_set_property does not exist → use material_set_float/material_set_color/etc. on the material, not the shader
• shader_apply / shader_assign do not exist → use material_set_shader to change a material's shader
• shader_get_properties returns shader property definitions (name/type/range), not current values → for material instance values use material_get_properties
• Shader names are case-sensitive and path-like: "Standard", "Universal Render Pipeline/Lit", not "standard" or "URP Lit"

Routing:

• For material property changes → use material module
• For shader keyword control → material_set_keyword (material module)
• For global shader keywords → shader_set_global_keyword (this module)

Skills Overview

Skills

shader_create

Create a shader file from template.

Templates:

shader_read

Read shader source code.

Returns: {success, path, content}

shader_list

List all shaders in project.

Returns: {success, count, shaders: [{name, path}]}

shader_find

Find a shader by name.

Returns: {success, name, path, propertyCount}

shader_delete

Delete a shader file.

shader_get_properties

Get all properties defined in a shader.

Returns: {success, properties: [{name, type, description}]}

shader_check_errors

Check shader for compilation errors.

Returns: { shaderName, hasErrors, messageCount }

shader_get_keywords

Get shader keyword list.

Returns: { shaderName, keywordCount, keywords: [{ name, type }] }

shader_get_variant_count

Get shader variant count for performance analysis.

Returns: { shaderName, subshaderCount, totalPasses }

shader_create_urp

Create a URP shader from template (type: Unlit or Lit).

Returns: { success, shaderName, path, type }

shader_set_global_keyword

Enable or disable a global shader keyword.

Returns: { success, keyword, enabled }

Example Usage

See ../../recipes/shader/<command>.md for C# templates.

Recipe path rule: ../../recipes/shader/<command>.md

Best Practices

1. Use consistent shader naming (Category/Name)
2. Organize shaders in dedicated folder
3. Start with templates, modify as needed
4. Test shaders in different lighting conditions
5. Consider mobile compatibility for builds