game-assets

Meowa Game Assets

Plan a game or create game-ready visual and audio assets. For game concepts, systems, balance, market research, or structured design documents, use the Game Designer module. For assets, establish the final asset contract first, choose the smallest suitable capability, and combine modules only when the downstream command accepts the upstream output.

Establish the asset contract

Determine these requirements before selecting a command:

• Runtime asset type: sprite, prop, UI, texture, tileset, map layer, animation, video, sound, or music.
• Art representation: pixel or HD.
• Final dimensions, sprite-cell size, count, aspect ratio, transparency, and file format.
• Deliverable structure: one asset, a variant pack, sprite sheet, directional set, layer set, animation, or reusable atlas.

Treat preset-defined dimensions and output counts as fixed contracts. Do not imply that prompt wording can override them.

Write simple natural-language prompts

Meowa capabilities use advanced generative models that understand ordinary natural language. Describe the required asset as simply and clearly as possible. Include only details that materially affect the deliverable, such as the subject, action, viewpoint, material, or relationship between elements.

Do not use legacy diffusion-style prompt engineering: no long keyword stacks, separate positive and negative prompt blocks, repeated quality terms, token weights, sampler syntax, or excessive camera and rendering jargon. These additions can interfere with the model's own interpretation and reduce consistency. Start with the shortest sufficient prompt, inspect the result, and add one necessary constraint at a time only when the output proves it is needed.

Apply game-art fundamentals

Pixel art

• Treat the pixel grid as part of the design, not merely as image resolution.
• Keep animated characters, monsters, and similar frame-based assets at 128×128 or smaller whenever practical. Larger pixel assets raise animation cost and often reduce generation or frame-edit consistency. Reserve larger pixel canvases mainly for maps, character illustrations, portraits, and other assets that do not need frame animation.
• When padding a 64px pixel character for animation, prefer a final canvas no larger than 128×128. Padding may be set independently on the top, down, left, and right, but a pixel-animation canvas above 256px on either axis is invalid and must not be submitted.
• When visual inspection is available, inspect the character bounds, facing direction, and intended motion before choosing animation padding. Leave some top space for jumps and some forward space for attacks; use only enough room for the action rather than making every canvas unnecessarily large.
• Treat pixel assets generated by Meowa as already perfectly pixelated. Do not run standalone pixelation on them again.
• Use pixel-native generation, editing, cleanup, and animation paths for pixel assets.
• Preview only at integer zoom with nearest-neighbor sampling. Never smooth or shrink pixel art merely for display.
• Inspect transparency and every sprite-sheet cell at native resolution.