cuozg/unity-spec
skills/unity-spec/SKILL.md
Investigate Unity projects and generate per-feature Game Design Specification docs in Docs/Specs/. Supports Full GDD, single Feature Spec, and Update mode that diffs existing specs against the codebase. MUST use when the user asks for a game spec, GDD, game design document, feature specification, stale spec update, per-feature spec split, or structured design documentation for a game concept. Also use to document mechanics, systems design, progression, UX/UI flows, or technical constraints. Do not use for technical design docs or system docs (unity-document), task planning (unity-plan), codebase investigation without spec output, or project scaffolding.
$ install --global
skillsauthnpx skillsauth add cuozg/oh-my-skills unity-specInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 4:06 AM121.3s6 files scanned
SKILL.md
- name:
- unity-spec
- description:
- >
- author:
- kuozg
- version:
- 2.0
unity-spec
Investigate Unity projects and produce per-feature Game Design Specifications. Each feature gets its own file in Docs/Specs/.
Triage
| Signal | Mode |
|--------|------|
| New game concept, multiple features | Full GDD — index + per-feature files |
| Single feature for an existing game | Feature Spec — one FEATURE_NAME.md |
| Existing spec outdated after code changes | Update — diff codebase vs spec, patch |
When ambiguous, ask: "Full game spec or just one feature?"
Output Rules (non-negotiable)
- Directory:
Docs/Specs/ - Feature files:
Docs/Specs/FEATURE_NAME.md(e.g.,Combat_System.md,Inventory.md) - Index file (Full GDD only):
Docs/Specs/_INDEX.md - Naming: PascalCase with underscores for multi-word features
- One feature per file — never combine unrelated features
Workflow
After triage, load the mode workflow:
read_skill_file("unity-spec", "references/workflows.md")
Follow the steps for the selected mode exactly. Every mode shares these gates:
- Scan — check
Docs/Specs/for existing specs - Investigate — deep codebase scan before writing (cite
file:line) - Draft — fill templates completely, mark gaps
[ASSUMED] - Review ⛔ BLOCK — present to user, wait for approval
- Save & Validate —
run_skill_script("unity-spec", "scripts/validate_spec.py", arguments=[<path>])
Templates
- Index:
read_skill_file("unity-spec", "references/gdd-template.md") - Feature:
read_skill_file("unity-spec", "references/feature-template.md")
Shared Rules
- Investigate actual codebase before writing — no speculation
- Cite
file:linefor every reference to existing code - Mark assumptions
[ASSUMED], updates[UPDATED: reason] - No TODO/TBD/FIXME in output
- Imperative language; no "we should" or "you could"
- Full GDD: at least 3 Mermaid diagrams across all files
- Feature Spec: at least 1 Mermaid diagram
- No C# code stubs — architecture-level descriptions only
Standards
Load unity-standards for architecture context:
code-standards/architecture-systems.md— patterns, dependencies, eventsplan/investigation-workflow.md— file tracing, call chainsother/mermaid-syntax.md— diagram syntaxother/unity-mcp-routing-matrix.md— MCP tool routing
Load via read_skill_file("unity-standards", "references/<path>").
Related Skills
cuozg/unity-image-gen
tools
VerifiedTrustedCommunity
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
4SKILL.mdUpdated May 29, 2026
cuozg/unity-technical
tools
VerifiedTrustedCommunity
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
4SKILL.mdUpdated May 26, 2026
cuozg/unity-mcp-orchestrator
tools
VerifiedTrustedCommunity
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
4SKILL.mdUpdated May 21, 2026
cuozg/goal-todo
development
VerifiedTrustedCommunity
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.
4SKILL.mdUpdated May 21, 2026