Universal Modder prompt library

Use these prompts with an installed coding agent. This library supports single-player modding only with games you own. Back up saves before changes and ask for one small verified slice before expanding the result. Start with installation; game reports can help narrow the goal.

A: README “Try it” prompts

The following five prompts are copied verbatim from the README “Try it” section. They are attributed examples, not terminal commands. Apply the single-player, backup and small-slice instructions above when using them.

Example 1

Mod Terraria: add a homing missile launcher and a tactical nuke that craters the world. Make the sprites with fal.

Example 2

Make a new civilization for Age of Empires II with a unique unit rendered from 3D.

Example 3

Put real Minecraft inside GTA V story mode. Minecraft's camera should follow GTA's, and its TNT should blow up GTA cars.

Example 4

Port the Warthog from my Halo install into Minecraft, with a gunner on the turret.

Example 5

What engine is `C:\Games\Foo`, and has anyone modded it before?

B: Our templates by goal

These are original templates, not upstream examples or guaranteed capabilities. Replace every [placeholder]. Their planning order follows the mod-any-game skill and mashup-mods skill.

Add an item or weapon — template

I own [game] and want [one item or weapon] in single-player only. Identify my installed version and loader, search matching field notes, and explain a suitable route before changing files. Back up saves before changes. Build one small slice: make the item appear and demonstrate [one behavior] in a separate test setup. Check the real game and record what remains untested before expanding.

Port something between games — template

I own [host game] and [donor game]. For single-player only, bring [one object or mechanic] into the host. Search notes for both versions and choose the lightest route for [appearance or behavior]. Back up saves before changes. Use one small slice first, verify its scale and behavior in the real host, and explain limitations before adding more.

Merge two games — template

I own [host game] and [guest game]. Plan a single-player mashup for [one interaction]. Compare a content port, a passthrough bridge and a rebuilt simulation before choosing. Back up saves before changes. Define camera, player ownership, coordinates and shutdown behavior. Build one small slice first and verify that interaction in the real games before expanding. Stop and report if the route cannot stay single-player.

Identify the engine — template

For my owned game at [installation path], identify the engine, version, existing loaders and matching field notes for single-player modding only. Begin with read-only reconnaissance. Before any later changes, back up saves and propose one small slice with a real in-game check. Explain uncertainty and avoid changing files until the route is understood.

Turn a prompt into a test

Specify the smallest behavior you can observe: one spawned item, one object at the right scale, or one interaction between the games. Ask what a successful screenshot, game log or repeatable scene would prove, and what it would leave untested. The verification oracles note distinguishes fast harnesses from real-game verification.

For a Minecraft starting point, see Minecraft reports. For a bridge, read Minecraft in GTA V and merge games with AI. If setup fails, consult troubleshooting.