Cocos Creator UI Design Transfer

I’m migrating a batch of web-based mini games built with Cocos Creator 2.4 into my own client and only need the visual layer moved over. You would open the existing project, pull out every UI element, then recreate or import those pieces so they appear in the correct positions inside my client scene files.

What I’ll hand you
• Spine Animation files that contain all graphical states for the screens, plus reference images where useful.

Scope
• UI elements only—buttons, panels, icons, text frames, progress bars, etc.
• No gameplay scripting, data wiring, or networking; I connect all logic afterward.

Environment
Cocos Creator 2.4 is mandatory so the meta data and prefab structure stay intact. If you prefer working in a newer branch, please be sure you can export assets back to 2.4 compatibility.

Timeline & payment
Each mini game is lightweight; once you know the flow, it usually takes under an hour. I’m setting the rate at $100 per mini game, and a typical project contains between five and ten games. We can settle milestones game-by-game so you get paid as we go.

Deliverable
For every mini game I expect the updated .fire/.prefab files (or scene equivalents) dropped into my repo with assets correctly referenced and laid out, ready for me to attach scripts. A quick screen recording showing the UI rendered in the simulator is all I need for sign-off.

If you already live inside Cocos and Spine, this should feel refreshingly simple. Let’s get these layouts ported and move on to the fun parts.