- Home
- Skills
- Dev Gom
- Claude Code Marketplace
- Unity Template Generator
unity-template-generator_skill
- C#
72
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill dev-gom/claude-code-marketplace --skill unity-template-generator- SKILL.md2.2 KB
Overview
This skill generates production-ready Unity C# script templates for common needs: MonoBehaviour components, ScriptableObjects, Editor scripts, and test files. Templates follow Unity conventions, include performance and safety patterns, and come with configurable placeholders for quick project integration. Use it to standardize new files and accelerate boilerplate creation.
How this skill works
The generator produces templated C# files populated with placeholders like {{CLASS_NAME}}, {{NAMESPACE}}, and {{DESCRIPTION}} so you can quickly instantiate properly structured scripts. Each template embeds best practices: serialized fields, component caching, OnValidate checks, XML docs, and organized regions. For Editor scripts it asks your UI preference (UGUI or UI Toolkit) and for tests it scaffolds NUnit/PlayMode patterns with Setup/TearDown and Arrange-Act-Assert sections.
When to use it
- Creating new MonoBehaviour components with lifecycle boilerplate
- Defining ScriptableObject assets with validation and asset menus
- Scaffolding custom Editor inspectors or editor windows
- Generating unit and playmode test skeletons
- Setting up consistent script structure across a project
Best practices
- Pick descriptive class names and proper namespaces to avoid collisions
- Use serialized private fields with properties for encapsulation
- Cache component references in Awake/OnEnable; avoid GetComponent in Update
- Include OnValidate and null checks to catch issues early in the editor
- Choose UI system (UGUI vs UI Toolkit) for editor scripts before generating to match project style
Example use cases
- Add a new enemy MonoBehaviour with cached components and Gizmo helpers
- Create a configurable GameSettings ScriptableObject with CreateAssetMenu and cloning
- Generate a custom inspector using UI Toolkit or UGUI to speed iteration
- Produce NUnit PlayMode tests with Arrange-Act-Assert and performance assertions
- Bootstrap a consistent file layout when onboarding new developers
FAQ
Yes. Templates use placeholders like {{CLASS_NAME}} and {{NAMESPACE}} so you can supply values or adjust template files to change defaults.
Which template should I use for editor customization?
Use the Editor Script template. It prompts for your UI choice (UGUI or UI Toolkit) and outputs a ready-made inspector or window scaffold.