cuozg/unity-localization
skills/unity-localization/SKILL.md
Implement, inspect, and validate Unity localization for locale setup, string tables, localized assets, font fallback, RTL handling, UI overflow, missing translations, and localization QA. MUST use for Unity Localization package work, multilingual UI/content checks, fallback behavior, and text coverage validation. Delegate package setup to unity-package-manager when installation or removal is required.
$ install --global
skillsauthnpx skillsauth add cuozg/oh-my-skills unity-localizationInstall 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: May 7, 2026, 3:14 AM266.9s1 file scanned
SKILL.md
- name:
- unity-localization
- description:
- Implement, inspect, and validate Unity localization for locale setup, string tables, localized assets, font fallback, RTL handling, UI overflow, missing translations, and localization QA. MUST use for Unity Localization package work, multilingual UI/content checks, fallback behavior, and text coverage validation. Delegate package setup to unity-package-manager when installation or removal is required.
- author:
- kuozg
- version:
- 1.0
unity-localization
Support multilingual Unity projects by discovering localization setup, making targeted changes, and validating content coverage and UI risks.
When to use
Use for:
- Locale setup and selected locale behavior.
- String tables, asset tables, localized assets, and localized references.
- Font fallback and glyph coverage.
- RTL language considerations and mirrored UI risks.
- Localization QA, missing translations, fallback behavior, and text overflow checks.
Discovery
- Check
Packages/manifest.jsonandPackages/packages-lock.jsonforcom.unity.localizationbefore assuming the package exists. - Search for localization tables,
LocalizationSettings,LocalizedString,LocalizedAsset, locale assets, and table collections. - Inspect UI text components and fonts used by localized screens.
- Identify source-language ownership and product copy guidance before rewriting user-facing text.
- If Unity Localization is missing and setup is required, delegate package installation to
unity-package-manager.
MCP tool usage
- Use
ManageAsset(Search/GetInfo)to locate localization settings, tables, locales, fonts, prefabs, and scenes. - Use
ManageGameObject(GetComponents)to inspect UI text components in scenes or prefabs. - Use
PackageManager_GetDatafor package metadata; delegate package changes tounity-package-manager. - Use
ReadConsoleorGetConsoleLogsafter localization asset or package changes. - Use scene capture tools when validating visual overflow or RTL layout.
Safety rules
- Do not assume Unity Localization is installed without checking package configuration.
- Do not rewrite user-facing text without explicit product guidance.
- Preserve table keys unless the user asks for key migration.
- Prefer adding missing entries over renaming existing keys.
- Treat RTL layout changes as visual/UI work and validate them in context.
Validation
Verify:
- Required locales and table collections exist.
- Missing translations, missing keys, and fallback entries are identified.
- Fallback behavior is configured for absent translations or assets.
- Font assets cover target language glyph ranges or have fallback chains.
- UI text does not overflow or truncate in target languages where visual validation is requested.
- RTL languages have alignment, ordering, and layout risks documented.
- Unity console has no localization package, table, asset, or serialization errors.
Boundaries
- Delegate package installation/removal to
unity-package-manager. - Delegate UI construction to
unity-uitoolkitorunity-codedepending on UI stack. - Delegate manual QA test plans to
unity-test-case. - Delegate generated localized art/audio to relevant asset skills.
Handoff
Report localization package state, assets inspected, missing coverage, fallback/font/overflow findings, and recommended next translation or UI QA steps.
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