Try for free
Learn/Guides/Seasonal event art

How to reskin your mobile game for a seasonal event with AI

Written by Avia Shavit, Product Lead, Genie Labs

Workflow · 6 prompts · Last updated Oct 26, 2026

→
1Seasonal reskin
→
2Outfit change
→
3Lighting change
4Icon set
NEW EVENT
5Announcement post

A seasonal event needs the whole game to look different for a few weeks: buildings, items, characters, UI, the lobby and the post that announces it. The fastest way to keep all of that consistent is to approve one reskin plan on one hero asset, then chain five prompts that apply the same plan everywhere: seasonal reskin, outfit change, lighting change, icon set and announcement post.

Key takeaways
Plan first, generate second. Approve a reskin plan on one hero asset before touching the rest.
Every later step gets the first approved reskin as a reference. That's what makes it one event, not ten.
Change what exists instead of drawing new art: costumes on existing characters, new light on existing scenes.
Save the plan as a skill and next year's event starts from it.
In Genie, the plan, the references and your characters live in one place, so the whole team reskins to the same rules.

Why does this matter for LiveOps?

In a live game, the calendar is the product. Themed events are some of the most reliable moments in the year, and also some of the first to get cut in planning, because the art list is long and the window is fixed. An event you can make in days is a test. One that takes a quarter is a bet you can't lose. This workflow is about making it the first kind.

How do you reskin for an event, step by step?

1

Step 1: Approve a reskin plan on one hero asset

Pick the asset players see most, often the main building or the lobby. Run Seasonal reskin, but first ask Genie's agent for a plan: which elements change, which themed details get added, which colors shift. Approve the plan, then the reskin. This approved pair is the reference for everything else.

→
PromptSeasonal reskin →
2

Step 2: Put the cast in costume

Run Outfit change on each event character. Describe the costume specifically (material, color, key pieces) and keep pose, face and background the same. Ask for several costumes in one request if you want options for the event's store bundle.

→
PromptOutfit change →
3

Step 3: Change the light, not the art

For a night event or a golden-hour summer, run Lighting change on existing scenes. Name the light source and direction, like "moonlight from the upper right, every window glowing warm". The scene stays. The mood changes.

→
PromptLighting change →
The next event, across every asset, on the calendar. Try Genie
4

Step 4: Make the event's icons

Run Icon set for rewards, boosters and event currency, with your style picked by @ and the step 1 reskin attached as the reference for palette. Check every icon at 64px, then cut them out in one go with Batch remove background.

PromptIcon set →
5

Step 5: Announce it

Run Announcement post with the reskinned hero asset and a costumed character, headline under six words. Then run Resize for every platform so every channel gets its format on launch day.

PromptAnnouncement post →

The event at a glance

StepPromptWhat changesReference to attach
1Seasonal reskinHero asset gets the themeApproved plan
2Outfit changeCharacters get costumesStep 1 reskin for palette
3Lighting changeScenes get the event's lightOriginal scenes
4Icon setRewards and currencyStep 1 reskin
5Announcement postLaunch creative, every formatSteps 1 and 2

What goes wrong, and how do you avoid it?

The theme is too light. A pumpkin sticker on a building isn't an event. The plan in step 1 should change materials and details, not only add props.
The theme is too heavy. If players can't recognize their own buildings, ask the agent to keep the silhouette and change surfaces only.
Assets don't match. Always attach the step 1 reskin. Without it, each asset gets its own interpretation of "Halloween".
The honest read: AI won't decide what your event is about. The theme, the story and the offer are still your team's calls. What it removes is the reason good event ideas get cut: too many assets for the window.

Where does Genie fit?

Genie holds the pieces that make an event consistent: your characters and styles behind @, the approved plan saved as a skill, and the canvas where the first reskin becomes the reference for the rest. One system across the store, the meta, CRM and social, so the event looks like one event everywhere players meet it.

FAQ

As many as the event needs. Run them in batches with the step 1 reskin attached each time.

Keep reading

All guides →
Full album,onestyle.
Card albumWorkflow · 5 prompts

How to build a collectible card album for a mobile game with AI

A workflow for card collection features: set the album's look, generate the cards in consistent batches, add rarity, make reward icons and cut out.

Every offer,onbrand.
Offer artWorkflow · 6 prompts

How to create and test in-game offer art with AI

A workflow for offer pop-ups and store packs: currency in the art, a clear pack ladder, rarity tiers, color and copy variants, and every placement.

One hero,everypose.
Character kitWorkflow · 5 prompts

How to build a complete character kit for a mobile game with AI

A step-by-step workflow from one approved character to a turnaround, expression sheet, pose set, rig parts and idle loop, using five chained prompts.

Reskin your next event.

One approved plan. The whole event in the same look.

Try GenieBook a demo
Learn/Guides/{{ g.crumb }}

{{ g.h1a }} {{ g.h1b }}

Written by {{ g.author }}

{{ metaLine }}

{{ g.intro }}

Key takeaways
{{ k }}

{{ pre.h2 }}

{{ b }}

{{ b.n }}{{ b.k }}{{ b.v }}

{{ g.stepsH2 }}

{{ s.n }}

{{ s.title }}

{{ x.text }}{{ x.text }}{{ x.text }}

{{ c }}
{{ x.text }}{{ x.text }}{{ x.text }}

Why first{{ s.why }}

Prompt{{ pc.name }} →
{{ g.cta.a }} {{ g.cta.b }} Try Genie

{{ g.glanceH2 }}

{{ c }}
{{ r.n }}{{ r.p }}{{ c }}

{{ g.wrong.h2 }}

{{ g.wrong.intro }}

{{ x.text }}{{ x.text }}{{ x.text }}
{{ g.wrong.honest }}

Where does Genie fit?

{{ g.genie }}

FAQ

{{ x.text }}{{ x.text }}{{ x.text }}

{{ g.closing.a }} {{ g.closing.b }}

{{ g.closing.line }}