Start from the resource-pack contract
Microsoft’s custom-item walkthrough puts the PNG under textures/items and registers the identifier in textures/item_texture.json. The folder and JSON mapping are part of the implementation, so a beautiful image in the wrong location is not a finished item.
Keep the namespace, identifier and filename aligned. Test the item in a minimal development pack first, before mixing it into a large texture collection where a path or JSON typo is harder to find.
Choose the pixel grid for the job
A generated 512×512 image is useful as a concept board, store icon or high-resolution reference, but it is not automatically a native game texture. Pick a deliberate grid—such as 16×16 or 32×32 for a deliberately low-resolution look—then downscale with hard edges and repair silhouettes by hand.
If the image will appear in a wiki, video or server store rather than inside the game, keep the larger master and create a separate in-game derivative. One source file should not be forced to serve every surface.
Design with the texture budget in mind
Microsoft’s performance guidance emphasizes total texture pixels, the number of texture handles and the cumulative cost of a pack across devices. A few oversized images can consume far more memory than their visual importance suggests, so measure the pack after adding a new item family instead of judging one file in isolation.
Keep repeated items visually simple, reuse a compact palette and remove unused variants. If a pack targets lower-end phones or consoles, test there before shipping a high-resolution promotional master as the final runtime texture.
Prompt for an asset you can finish
Name the item silhouette, viewing angle, material cue, outline treatment, palette size and target pixel grid. Ask for a transparent or plain background and no baked UI text. For a collection, list every item in one visual family so highlights and edge weights do not drift from one generation to the next.
GUIFoundry’s Minecraft modes are best used to establish a coherent concept family. Export the master for promotion, then make the final resource-pack derivative with the exact path, JSON mapping and in-game test in view.