菜单
Create, pack, configure, integrate, debug, and validate LayaAir 3.3 atlas frame animations for this project. Use for idle/walk/attack sprite art, one-PNG-plus-atlas resources, CharacterAnimation configuration, ResFrameAnimation playback, team-color mask synchronization, or unsupported suffix and null sourceWidth errors.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | laya-frame-animation-builder |
| description | Create, pack, configure, integrate, debug, and validate LayaAir 3.3 atlas frame animations for this project. Use for idle/walk/attack sprite art, one-PNG-plus-atlas resources, CharacterAnimation configuration, ResFrameAnimation playback, team-color mask synchronization, or unsupported suffix and null sourceWidth errors. |
Build frame animation as one large PNG plus a .atlas; never ship an undescribed grid or many loose frame files.
DESIGN.md and README.md files.tools/art/build_character_frame_atlas.py; do not manually slice final resources..png suffixes on every atlas frame name and runtime subtexture URL.Config/csv/, then run the Config exporter. Never hand-edit generated JSON.ResourceMgr and ResFrameAnimation; pass cached subtexture URLs to Laya.Animation.images.assets/; never add an assets/ prefix..meta files.Laya.Animation; .atlas defines its subtextures.unsupported suffix followed by null sourceWidth.actionName, inclusive startFrameIndex, and endFrameIndex. The owning character resource supplies file context; do not duplicate characterId in every action record. Playback is continuous through the range; do not add nextAction, event markers, or an action graph unless a later confirmed requirement needs them. The owning Entity update advances its ResFrameAnimation with scaled scene delta time; ResourceMgr owns loading, references, pooling, and disposal. Defer a centralized renderer until large-unit profiling proves it necessary.Design, implement, and verify a Laya game feature that crosses Client, Protocol, Gateway, or Sever boundaries. Use for server-authoritative state, request/response or push messages, login/reconnect synchronization, rewards, inventory, wallet, battle settlement, identity, exact integers, payload Schema changes, or any change where client and server must ship one compatible contract. Enforce ownership, security, staged gates, generated message IDs and payloads, runtime boundary validation, and end-to-end evidence; do not use for a purely local UI, art, or service-internal refactor with no cross-end contract.
Use when a LayaAir battle entity has persistent animation, position jitter, missed attacks, stale state, or behavior that differs across AI scheduling, FSM update, movement/avoidance, and SkillAgent execution.
Design, generate, assemble, revise, audit, and clean up LayaAir 3 UI screens and reusable components. Use when Codex needs an end-to-end independent-screen workflow, panel/button/background art, nine-slice planning and sizeGrid validation, PNG slicing, common-resource reuse, .lh/.ls assembly, res:// and meta handling, visual validation, or redundant UI asset removal.
Navigate and maintain this project's scoped README.md, DESIGN.md, and PlanAndStatus.md system. Use when deciding what to read for a task, evaluating next development work, recording a current plan, promoting completed outcomes into durable documentation, deleting completed plans, or checking documentation scope and conflicts.