Skip to main content

✍️ Effective Prompting

Ludus reads your project and plans multi-step work before it edits anything. Because of that, prompting is about stating the goal clearly, then reviewing the plan Ludus proposes. This page covers how to write requests that reduce back-and-forth.

State the goal, then review the plan​

Describe the outcome you want in plain language. For larger requests, Ludus breaks the work into steps in the plan panel and can split parts across sub-agents. Read the plan before it runs and adjust the steps if the scope is wrong. See Planning, Memory & Sub-agents.

Example: "Add a sprint and stamina system to the player character, then hook stamina drain to the existing movement input." Ludus proposes a plan (variable, drain logic, input wiring) that you review before it starts.

Be specific about what to change and what to keep​

Name the target asset, graph, or system, and state what must stay untouched. This prevents unwanted restructuring.

  • Good: "In the Fire Weapon event, consume 5 ammo instead of 1, and keep the sound and recoil logic exactly as it is."
  • Vague: "Fix the shooting."

Iterate and interrupt​

Watch the work as it runs. If Ludus takes a wrong turn, interrupt it and correct course rather than waiting for the full run. You can refine the request and let Ludus replan from where it stopped.

Confirm external dependencies are active​

If your request relies on a C++ class, a specific plugin node, or a FAB dependency, make sure that plugin is enabled and the node is valid in the current editor context before you prompt. Ludus cannot wire a node that the editor does not expose.

Prompting for 3D​

  • Prompt the reference image first, then the model. The mesh follows the image, so describe the visual look of the object clearly before generation.
  • Break complex scenes into individual assets. Generate a scene concept image first, then ask Ludus to build the individual objects one at a time.

See 3D Models & Transforms and Images.

Keep prompts specific to reduce cost​

Specific prompts need fewer regenerations and less back-and-forth, which lowers credit use. See How to Reduce Credit Costs.

Attach images and documents​

Attachments improve results. Attach a reference image, a screenshot, a spec document, or a data table so Ludus works from your source material instead of inference. See Chat, Context & Attachments.