Make assets that belong in this game and work in its runtime. Preserve the existing art direction and useful assets. Produce only what the task needs; an individual pickup or animation does not require replacing the whole game.
Establish the target
For a new art or sound direction, inspect at least two relevant games or authored references online. Actually view images or gameplay for visual assets, and listen to relevant examples when designing sound. Search snippets, descriptions, and filenames do not count. Study silhouette, palette, materials, motion, readability, or sound character as appropriate, including how the asset works alongside others.
Keep a brief note of sources, images or timestamps inspected, and the qualities to adapt or avoid. Check that both references were examined before choosing the direction. If a fetch fails, try another source and another available access method, such as a browser or direct download. Use the normal approval path for sandbox-blocked operations; one tool's network failure does not establish that research is unavailable. Disclose any evidence still missing after alternatives. Reuse established references for small additions. Match the game's identity without copying another creator's distinctive assets.
For a substantial set, make a representative asset or concept first and inspect it in context before expanding the set. Record the shared palette, scale, camera, material, animation, or sound constraints that will keep production consistent. Extra concept sheets are useful only when they resolve a real design question.
Produce and integrate
Choose tools for the result: image or audio generation, authored SVG or sprites, Blender, a suitable model generator, procedural geometry, shaders, or synthesis. Use available specialist skills. Verify unfamiliar tool capabilities before depending on them. Prefer a suitable working tool over blocking the task on an optional service.
Use purpose-made imagery, shapes, textures, and sounds where they improve the result. Procedural work and generated files need the same quality checks. Simple art is valid when intentional; generic placeholders do not become finished assets just because they load.
Keep editable sources and runtime exports organised. Check dimensions, units, pivots, transparency, spritesheet frame boundaries, animation timing, material compatibility, and resource cost as relevant. For models, use the views needed to establish shape, then inspect the exported model in the target renderer. For audio, check duration, clipping, loop boundaries, and levels in the mix. Keep required attribution and usage rights with third-party assets.
Check it in the game
Inspect integrated assets at their actual gameplay scale, against representative backgrounds, and in motion when animated. Check that players can distinguish important objects and states, and that the set looks or sounds consistent. Fix observed seams, unreadable silhouettes, bad deformation, awkward transitions, or overpowering effects; then inspect again.
For an asset-only request, use a representative preview and say that runtime integration remains untested. Do not claim to have heard audio from its waveform or viewed animation from one still. Deliver the requested files and briefly identify what was checked. Keep tests silent through polite-browser-use where applicable; do not publish or upload the game unless requested.