Skip to content

t1k:reskin

FieldValue
Modulet1k-engine-bridge
Version3.18.40
Efforthigh
Tools—

Keywords: apply art, art spec, asset manifest, đổi giao diện game, game reskin, mockup first, re-skin, reskin, reskin wave, thay art, thay skin, ui reskin

/t1k:reskin
[game project | stage 0-8 | wave to apply]

Re-skin a shipped game (replace its art with new art) without breaking behaviour, layout, or the original assets. Engine-agnostic: the stages hold for Unity, Cocos, Godot, and web. Engine-specific mechanics appear only as clearly marked examples.

Disambiguation. This skill is the end-to-end workflow (capture → manifest → mockup → spec → waves → apply → QA). For which presentation assets an artist may self-serve inside one feature module, see t1k-game-arch § “Presentation-Layer Reskin Contract”. Neither repeats the other.

IntentLoad
Run the whole reskin, or “what comes after stage 4?”references/workflow.md
Classify an asset (9-slice, tile, tint mask, shared, out of scope)references/asset-types.md
Paste finished art into the build, diff, verify hashesreferences/apply-into-game.md
Review a screen before sign-offreferences/qa-checklist.md
Agree scope BEFORE starting a gamereferences/decide-first.md
Printable PDF checklist for artists and the lead (sign-off, per-wave rows)references/checklist-pdf.md
Figma template: reference vs NEW cards, Figma MCP recipereferences/figma-template.md
Export original 3D objects, environment, level layouts (FBX + renders)references/reference-export-3d.md
  1. Original assets are read-only. Keep them in their own folder, never edit or delete them. Art maps 1:1 by name and size. Prove it by folder hash, not by remembering.
  2. Mockup first, art second. A playable build on original assets is the baseline; every later change is compared against it.
  3. Repeated work becomes a tool. Manifest, apply, pixel diff and screen render are re-runnable steps, never one-off manual edits.
#StageOwnerGate before moving on
0Capture flowDevEvery screen has an ID, in the original order
1Extract + health-checkDevGame builds; every missing item documented
2Asset manifestDevEvery asset has a type
3Playable mockupDevEach screen’s SSIM vs its screenshot is above the agreed threshold
4Lock styleArt + leadLead signs off the style before bulk generation
5Art specDevArt confirms the spec is understood
6Reskin in wavesArtEach wave reviewed before the next
7Apply into the gameDevPixel diff clean, original folder hash unchanged
8QA, fix, packageDev + ArtNo blocking defects, no new runtime errors, lead accepts

Stages 3 and 4 can run in parallel. Full work, outputs and gate detail: references/workflow.md.

  • NEVER edit, move or delete the original-assets folder. It is the only reference for name and size, and the mockup baseline. A wrong paste is recoverable from it; a damaged original is not.
  • NEVER scale a wave without a smoke gate. Generate ~8 assets (one per group), show them, get approval, then run the groups.
  • A shared sprite changes every screen that uses it. List its users in the manifest and QA each one, or a single paste breaks screens nobody looked at.
  • Dummy or missing shaders make all text render dark. Confirm the build renders text correctly at stage 1, before judging legibility anywhere later.
  • Reference images come from the project only, never generated. REF frames, PDF thumbnails and 3D renders derive from project files; concept art is never an original.
  • Prefab file names must equal the key that loads them, case-sensitive on Android.

Covers art replacement for an existing, playable game. Does NOT cover: building the game itself, gameplay/balance changes, audio, or authoring the original art. Out-of-scope asset groups (flags, fonts, ad logos, VFX) are decided per game before stage 0, see references/decide-first.md.

A gate that passed something QA rejected, or an apply trap not listed here, is a lesson: emit [t1k:lesson ...] so it lands in the ledger skills/t1k-rsi/ledger/gotchas/<skill>.md, and [t1k:skill-bug ...] for a defect in this skill’s own instructions.