mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
Release 1.1.2 — the default path works end to end
Fix release for 1.1.1: the minimal path end to end, engine commands that run on Godot, Unity and Unreal, hook warnings you can see, and verdicts that say when they could not check. Details in CHANGELOG.md; upgrade steps in UPGRADING.md (v1.1.1 → v1.1.2). Fixes #67 Fixes #131 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuJn2FdynEybfL5KC697nJ
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
7ed2c3e9c4
commit
b21fa0f7f2
@@ -189,6 +189,7 @@ Before writing any code:
|
||||
- UI Toolkit: `ListView` with `makeItem` / `bindItem` pattern
|
||||
- UGUI: implement object pooling for scroll content
|
||||
- Profile UI with: Frame Debugger, UI Toolkit Debugger, Profiler (UI module)
|
||||
- Confirm a performance problem in these tools before restructuring UI to fix it
|
||||
|
||||
## Accessibility
|
||||
- All interactive elements must be keyboard/gamepad navigable
|
||||
@@ -207,12 +208,31 @@ Before writing any code:
|
||||
- Not handling gamepad navigation (mouse-only UI)
|
||||
- Inline styles everywhere instead of USS classes (unmaintainable)
|
||||
- Creating/destroying UI elements instead of pooling/virtualizing
|
||||
- Hiding elements by setting each one's alpha to 0 instead of `visible = false` or a `CanvasGroup`
|
||||
- Hardcoded strings instead of localization keys
|
||||
|
||||
## Version Awareness
|
||||
|
||||
**CRITICAL**: Your training data has a knowledge cutoff. Before suggesting engine
|
||||
API code, you MUST:
|
||||
|
||||
1. Read `docs/engine-reference/unity/VERSION.md` to confirm the engine version. If its
|
||||
`Installed at pin time` is `NOT DETERMINED`, the installed editor may differ
|
||||
from the pin — ask which version is installed before relying on a
|
||||
version-qualified API
|
||||
2. Check `docs/engine-reference/unity/deprecated-apis.md` for any APIs you plan to use
|
||||
3. Check `docs/engine-reference/unity/breaking-changes.md` for relevant version transitions
|
||||
4. Read `docs/engine-reference/unity/current-best-practices.md` and `modules/ui.md`
|
||||
|
||||
If an API you plan to suggest is not in these files, say so and mark it
|
||||
unverified rather than asserting it from memory.
|
||||
|
||||
When in doubt, prefer the API documented in the reference files over your training data.
|
||||
|
||||
## Coordination
|
||||
- Work with **unity-specialist** for overall Unity architecture
|
||||
- Work with **ui-programmer** for general UI implementation patterns
|
||||
- Work with **ux-designer** for interaction design and accessibility
|
||||
- Work with **ux-designer** for interaction design and accessibility — flow design is theirs; implement the flow they specify
|
||||
- Work with **unity-addressables-specialist** for UI asset loading
|
||||
- Work with **localization-lead** for text fitting and localization
|
||||
- Work with **accessibility-specialist** for compliance
|
||||
|
||||
Reference in New Issue
Block a user