Only replace the appearance. Prefer adding native multi- Skeleton within the same Spine Skin, reusing the existing skeleton, animations, Mesh, and weights; do not expand the scope by redoing the character structure.
First determine whether it is still reskinning
Continue only when all of the following structures are frozen, and before starting, save the source project, exports, and Unity baseline evidence:
- Bone names, parent-child hierarchy, and Setup Pose.
- Slot names, order, and Draw Order.
- Attachment names, types, and occupancy relationships.
- Mesh vertices, triangles, UVs, weights, and Linked Mesh relationships.
- IK, Transform, Path constraints and their targets and order.
- All animations, events, and Attachment Timelines.
- Collisions, attack points, hit points, attachment points, and gameplay code.
If the new appearance must change any frozen item, the silhouette cannot be established within the existing Attachment/Mesh boundaries, the connection area cannot be reused, or the existing mesh shows obvious deformation errors, immediately return BLOCKED, list the conflicting objects and evidence, and hand off to a higher-scope character remake/skeletal animation task. Do not reduce the appearance, silently rename, change weights, change Attachment types, or lower acceptance criteria and then pass it off as reskinning.
Version and source project pre-check
- Read-only discovery of
.spinesource project, original textures, exported JSON/Binary, Atlas, UnitySkeletonDataAsset, AtlasAsset, materials, and runtime code entry points. - Record the Spine source project version, the actual Spine Editor version used for export, JSON/Binary format,
spine-unity/Spine Runtime package version, Unity/URP version, and current export settings. Check the official compatibility matrix or an existing successful export baseline; when versions do not match, keepBLOCKED, and do not guess compatibility or arbitrarily upgrade the source project. - If there is no writable source project that can be opened by the correct Spine Editor, immediately
BLOCKED. It is forbidden to directly tamper with exported JSON, Binary, or Atlas to fake a Skin, and it is also forbidden to substitute Unity runtime assembly for a formal source project Skin. - Check the existing Skin, Slot, Attachment, mesh, constraints, animations, collision/attachment points, and Unity reference list, and form a frozen list and SHA-256. Before starting, confirm the target output directory and single writer; do not overwrite the only valid source or the current stable export.
Embedded V0-V4 execution
V0-V4 are the scene and asset production stages; A0-A6 only indicate action risk. F2 records independent Spine/visual review, and F3 records Unity compilation, import, PlayMode, and asset evidence; only real visual tradeoffs use USER_DECISION。
V0 references the Visual Bible
Reference a Visual Bible that is still valid and covers this character. If it is missing, invalid, or insufficient in scope, return $unity-development-workflow to establish or select a global visual baseline; when a valid specification already exists, regenerating candidates is not mandatory.
V1 reskin sketch and structural mapping
- Produce a complete reskin sketch/graybox that can actually be viewed, as well as key poses such as standing, moving, and attacking that are sufficient to expose connection and occlusion issues.
- Draw the complete boundary of each part, occluded completions, connection areas, front/back occlusion, Clipping boundaries, and extreme bending margins; do not submit only a front-facing static half-body image.
- Submit item by item
skinId → slotName → attachmentNamemapping, indicating the Attachment type, existing Mesh/Linked Mesh, origin/Pivot, canvas, purpose, orientation, status, and expected Atlas Region. - Complete an independent visual/Spine review; when substantive trade-offs exist, request user confirmation of the current sketch, key poses, and mapping version. Do not enter V2 while the production boundary is not frozen.
V2 High Fidelity and Production Boundary
- Generate the complete high-fidelity character and representative key poses only based on the valid visual baseline and V1; do not secretly alter Slots, Attachments, outline boundaries, or occlusion design.
- F2 is performed by a non-author to review visual consistency, Spine feasibility, and UX/readability; check all poses, connection areas, outlines, layering, Clipping, color recognition, and animation readability.
- Freeze the high-fidelity, asset breakdown, mapping, and production specifications as the same V2 boundary; when visual trade-offs exist, bind them to the user's decision. Any boundary or mapping change generates a new version and re-validates the affected scope.
V2 Numbered Asset Map
- Analyze only the frozen high-fidelity original image, and completely number all visible parts and items explicitly requiring no production; missing labels, duplicate numbers, or items without mapping all block.
- Each item is fixedly recorded
skinId → slotName → attachmentName → sourceImage → atlasRegion, and record the same canvas, Pivot/origin, connection areas, complete occlusion completion, purpose, orientation, pixel dimensions, Alpha, PMA strategy, and acceptance poses. - Only after the asset map production boundary is frozen may each item be independently generated or redrawn by number. It is forbidden to crop, cut out, enlarge, or lightly retouch the high-fidelity rendering as the source image; it is forbidden to put the entire character rendering into the Atlas.
- For each item, verify the existing Attachment type, Mesh vertices/UV/weights, and Linked Mesh. When there is an obvious outline change, canvas/Pivot inconsistency, incompatible connection area, or the mesh cannot carry it, immediately
BLOCKED, and do not modify Mesh, UV, or weights to solve it. - For each source image, separately validate transparent edges, complete outline, connection areas, orientation, dimensions, sampling, color, and deformation in key poses before allowing entry into V3.
V3 Batched Production Record
Only after the complete V2 asset map and production boundary are frozen may batching be split. Batching is only execution scheduling and cannot replace any V0-V2 gate; all assets must still first complete full numbering, classification, mapping, and map confirmation.
- Establish a machine-readable JSON ledger within the project:
Artifacts/Spine/<characterId>/batch-ledger.json. Paths must be POSIX relative paths within the project root, and must not use absolute paths, paths outside the project, symbolic link segments, or temporary chat attachments; the ledger and evidence writes are maintained by a single writer. - The ledger root object records at least
ledgerVersion、projectId、characterId、sourceRevision、assetMapVersion、assetMapSha256、visualBibleVersion、visualBibleSha256, completeassetIds、batches, append-onlyeventsandoverallStatus。assetIdsmust be item-by-item identical to the current V2 map. - Each batch records at least:
taskId、skinId、batchId, a non-duplicateordinalstarting from 1, uniqueassetIds、dependsOnBatchIds、inputVersion/inputSha256、outputVersion/outputSha256、owner、singleWriter、status, creation/start/update times, validation/review/user decision evidence, failure and blocking reasons,recoveryPoint、unityVersion、spineEditorVersion、spineRuntimeVersion、exportFormat、supersedesandsupersededBy。 - Each V2
assetIdmust appear in and only in one currently valid batch; when creating batches, validate that the set is exactly equal to the V2 map, and prohibit omissions, duplicates, empty batches, or dependency cycles. Failed batches still retain their original asset ownership; when revising, create a newbatchIdand record the supersedes relationship. - Status may only advance in the order
PLANNED → READY → IN_PROGRESS → PRODUCED → REVIEWED → INTEGRATED → VALIDATED; on exception, enterFAILEDorBLOCKED, and must not writePASSor falsify completion. Immediately after batch creation, start of work, each artifact generation, review, Unity integration, and validation completion, append an event toevents, recording the time, executor, status, input/output hashes, and evidence path; overwriting old events or old evidence, or backfilling history from chat logs, is prohibited. - Before resuming a batch, re-read and verify the current V2 map/Visual Bible hashes, input/output hashes, dependency batch status, Spine/Unity export version, and single writer; if any mismatch occurs, invalidate and reopen the affected batch, record
supersedes/supersededBy, and do not continue based on conversational memory. - After all batches reach
VALIDATED, the full-batch mapping has no omissions, and V4 integration is complete, a full regression for the entire character must still be performed once: completeassetId → skinId → slotName → attachmentName → atlasRegionmapping, Atlas/material/PMA/Draw Call/texture memory, all animations and Attachment Timelines, default/new Skins, multi-instance isolation, extreme poses, Clipping, and occlusion. Only when the full regression actuallyPASSmay the overallCOMPLETEbe written; any failure or blockage must retain the ledger and return to the corresponding batch.
V4 Spine source project and Unity integration
- Add native Skins in the original Spine source project, reusing the frozen Skeleton, Slot, Attachment names/types, Mesh, weights, constraints, animations, and Attachment Timelines; only replace the region/image bindings for each Skin.
- Use the confirmed compatible Spine Editor and existing export configuration to repack the Atlas and export JSON/Binary. Output to the new version path and verify the frozen manifest before and after export; any structural difference is a failure.
- Keep Atlas Regions consistent with the V2 mapping. Explicitly use PMA or Straight Alpha; texture import, Atlas settings, and material Shader must use the same strategy, and mixing them in a way that causes black edges/white edges is prohibited. URP uses the currently
spine-unitysupported Spine/Skeleton Shader and correct material keywords; do not arbitrarily switch to an incompatible generic Shader. - Record Atlas page count, material/blend mode, Clipping, Draw Call, texture size, format, MipMap, and estimated/measured texture memory; new Skins must not increase the batch count with unbudgeted extra Atlas pages or materials. Introduce Addressables only when the user explicitly needs independent download, uninstall, or content packaging, and verify
SkeletonDataAsset, AtlasAsset, material, and texture reference atomic loading. - Switch Skins in Unity on the current instance: first confirm the target Skin exists; keep the original
AnimationStateand current Track, and do not rebuild or clear the animation state; for that instance'sSkeleton, set the Skin, restore the Slot setup pose, then reapply the current AnimationState. If the target Skin is missing, fall back to the default Skin and report it, do not write to the sharedSkeletonData, and do not let one instance's switch contaminate other instances. - After reimport, verify
SkeletonDataAsset, AtlasAsset, material, texture, GUID/address, Prefab/Scene references, and Console; do not useunity commandreturning success as a substitute for real verification.
Unity verification matrix
At minimum cover the following current-version combinations:
- Standing, moving, attacking, hit, death, and other key animations actually used by the project.
- Extreme bending, stretching, flipping, scaling, and mirroring conditions.
- Attachment Timeline switching, before and after events, and animation blending/interruption.
- Front/back occlusion, Draw Order, Clipping, transparent edges, blend modes, and color tinting.
- Default Skin, new Skin, missing Skin fallback, and multiple instances on the same screen using different Skins.
- Actual lifecycles such as Prefab/Scene reload, object pool reuse, disable/enable, and save recovery.
- Editor simulation of Atlas/material/PMA/URP display, Draw Call, texture memory, and applicable platforms.
First run EditMode/PlayMode, Editor/Game View, and the project's existing automated tests. Do not automatically launch Standalone, Player, or real devices; device acceptance can only be executed in a separate release Work Item after the user explicitly requests it.
Evidence, Invalidation, and Handover
- Changes to the Visual Bible invalidate the affected V1-V4; changes to V1 invalidate the affected V2-V4; changes to V2 mappings or source images invalidate the affected production items and V3/V4.
- Changes to the Spine source structure, export settings, Editor/Runtime version, Atlas, materials, GUID/address, or runtime switching logic invalidate the corresponding exports and Unity validation; if a structure-frozen item changes, exit this Skill and
BLOCKED。 - Save the freeze list, sketch/high-fidelity/asset map confirmation, item-by-item source images, Spine source revisions, export logs, diff reports, Unity references, tests, screenshots, performance, and failure evidence. Old approvals are for historical record only.
- On completion, report to the overall control the changed files, evidence of zero differences in fixed items, validation matrix results, Atlas/performance impact, items not run, and remaining risks; do not write missing Spine Editor, source project, license, Unity environment, or devices as passed.