Game Asset Production Sheet Generator

Create a production-ready visual reference sheet for {{asset_family}}.

Asset brief
{{asset_brief}}

Production constraints
- In-game view: {{game_view}}
- Art pipeline: {{art_pipeline}}
- Handoff target: {{engine_target}}

Image plan
1. Use a clean neutral background and an orderly grid. Keep identity, proportions, scale, palette, material, wear, and lighting consistent across every view.
2. Show only the views needed by the asset type: front/side/back and three-quarter for a character or creature; consistent-angle variants for props or weapons; one grid and silhouette weight for icons or UI.
3. Prioritize the silhouette at actual gameplay size. Preserve clear negative space around hands, weapons, feet, attachment points, and interactive edges.
4. Make material differences physically legible through roughness, edge treatment, thickness, seams, and wear—not through random decoration.
5. Keep the ground contact and pivot reference stable. For modular assets, expose connection surfaces and repeatable edges. For 2D assets, preserve clean alpha-safe boundaries and pixel density.
6. Do not render tiny labels, dimensions, logos, watermark text, HUD mockups, perspective distortion, duplicated parts, or decorative scenery. Put technical notes outside the generated image.

After the image, provide a concise handoff checklist for manual crop/separation, alpha cleanup, naming, pivot, collision or hitbox, rig/socket, texture channels, LOD or sprite import, and in-engine readability testing. State clearly which values still require human measurement.

Shared execution rules
- Use selectors as production constraints that change structure, limits, and acceptance tests.
- When current information matters and search is available, prioritize official engine documentation, platform policy, original sources, and primary evidence. State the as-of date and separate fact, inference, and invention.
- Do not copy protected characters, worlds, dialogue, UI, or a distinctive game/studio style. Translate intent into observable shape, material, color, camera, and rhythm.
- Treat generated output as concept or production reference. Before engine use, require human review of rights, resolution, alpha, seams, pivots, collision, rigging, performance, and accessibility.
- Work through analysis → draft → gameplay-readability and continuity check → minimal revision. Label assumptions or open questions instead of inventing missing values.