besty0728/unity-skills

Overview

This skill helps you create, read, and list shader files inside the Unity Editor from automated workflows. It provides quick template-based shader creation, reliable source reading, and project-wide shader discovery. Use it to standardize shader assets and speed up iterative shader development.

How this skill works

The skill exposes three operations: create a shader file from a chosen template, read the raw shader source from a given asset path, and list shader assets across the project with optional name filtering and result limits. Creation writes a new .shader file at the specified save path using Unlit, Standard (PBR), or Transparent templates. Listing scans project assets and returns names and paths; reading returns the file content for inspection or automated edits.

When to use it

• When you need to quickly scaffold a new shader using a common template.
• When automating asset pipelines that must inspect or modify shader source files.
• When auditing or documenting existing shaders in a project.
• When building tools that collect shader usage or prepare assets for build targets.
• When you want to enforce naming and folder organization across shader assets.

Best practices

• Use Category/Name naming (for example, Custom/MyShader) to keep shaders discoverable.
• Place shaders in a dedicated Assets/Shaders folder to simplify listing and maintenance.
• Start from provided templates (Unlit, Standard, Transparent) and iterate rather than writing from scratch.
• Test created or modified shaders under multiple lighting conditions and platforms.
• Keep mobile compatibility in mind: favor simpler lighting models and smaller shader variants for builds.

Example use cases

• Create an Unlit shader template at Assets/Shaders/MyUnlit.shader during automated project setup.
• Generate a PBR surface shader (Standard) for a new material pipeline and commit it to source control.
• Read shader source to perform automated refactors, insert custom includes, or validate keywords.
• List all project shaders matching a prefix (e.g., Custom) to produce an asset inventory or report.
• Build tools that replace or patch shader code before runtime packaging for different platforms.