X3 4gl Copilot

Invocation

• Use $x3-4gl-copilot when asking for explanation, generation, review, or troubleshooting.
• Ask for the artifact and goal explicitly, such as a routine, action block, transaction flow, join, or screen event.
• If the input contains client-specific names, preserve them only when the user provided them in the task.

Working rules

• Prefer the dictionary's normalized entry over ad hoc guesses.
• Keep generated code explicit: visible aliases, visible transaction outcome, visible fstat checks, visible labels.
• Avoid client-specific names and table abbreviations unless the user supplied them.
• When the corpus suggests a habit that lacks normative support, say so explicitly instead of presenting it as a rule.
• When reviewing code, prioritize bugs, hidden state, missing file guards, broken action routing, mask-state confusion, and transaction safety.

Generation defaults

• Use small examples with clear labels and comments only where structure would otherwise be ambiguous.
• Prefer patterns aligned with $ACTION, Subprog, Funprog, Local File, Link, Filter, Trbegin, and explicit screen-event wiring.
• Show error or status checks near the operation that can fail.

Coverage snapshot

The current generated dictionary contains 504 normalized entries across 12 categories.