Production field guide
A game-art handover developers can actually use
A useful art handover tells a developer where an asset belongs, how it behaves and how to know it works. Separate source files, review previews and runtime exports. The worked example below is fictional: agree dimensions and budgets with the actual game team.
Give every asset a screen and a state
“Win animation” is too vague to integrate. Specify whether it belongs in the base game, a feature, the result screen or a campaign. Identify its trigger, the information it communicates and the resting state it returns to.
In our fictional Aurora game, aurora_symbol_comet_idle.webp belongs in a reel cell. aurora_symbol_comet_win.json supplies its win treatment. aurora_background_portrait.webp is a separate portrait composition. These example names do not refer to a partner game.
Separate the three deliverable groups
Source contains editable illustration, rig or compositing projects and their dependencies. Review contains stills and videos an approver can inspect without an engine. Runtime contains the exports the agreed build can load.
A review MP4 does not replace an animation export. A flattened image does not replace agreed editable source. Record the tools and versions required to reopen work, and check third-party licences.
- source/ — editable work and licensed dependencies
- review/ — labelled stills, videos and approval notes
- runtime/ — agreed game-ready exports
- manifest — filename, version, owner, rights and accepted hash
Work through one register row
Our example comet symbol is a 512 × 512 transparent WebP with a central pivot, a 32 px safe margin and an illustrative 80 KB ceiling. These are fictional constraints, not universal specifications.
The downloadable CSV has three worked rows. Replace each example limit with the constraints agreed for your renderer, device, visual quality and download budget. Record actual exported size alongside its budget.
Define animation as behaviour
The example comet win starts from idle, plays once for 900 ms and emits a highlight marker at 200 ms. A skip request returns it to idle and emits completion once. It must not leave gameplay waiting for a missing event.
Agree the trigger, initial state, loop rules, event markers, interruption and final state together. Specify which system owns sound playback and what happens when the sequence is skipped.
- Trigger and start pose
- Duration, loop and event markers
- Skip, interruption and reduced-motion treatment
- Completion signal and final resting state
Review portrait as its own composition
Keep the play area, important character action and controls visible together. A desktop screenshot cropped into a phone frame does not prove a portrait design. Review the narrowest supported layout with real controls, text and feedback.
Check long translated labels, large win values and changing browser viewport height. Show ordinary play and the busiest feature state, with safe areas marked.
Integrate a small slice first
Deliver one symbol, one animated character and one transition first. Have the developer load them in the actual build, check the mobile composition, exercise interruption and confirm export settings before the full set.
Freeze a versioned manifest with hashes, limitations and the approver’s decision. A replacement gets a new version and change note. PlayBeSpoke workspace comments and approvals attach to specific file versions, keeping decisions traceable.
Put it into practice.
Use these editable planning resources with your team. They are examples, not a quote, certified model or committed delivery scope.
Download the production handover register ↓Download a fictional slot brief example ↓Worked asset register · CSV ↓Animation contract example · JSON ↓Commission art and animation ↗See the visual review journey ↗Your project. One shared space.
Shape your idea in Creator, review the visuals and agree the next step in your private client studio.