x3-4gl-copilot - SKILL.md Agent Skill

name: x3-4gl-copilot description: Comprehensive Sage X3 4GL skill grounded in the EnterScript curated X3 knowledge base, with a self-contained dictionary, thematic knowledge router, syntax guide, entry-point guidance, project idioms, UI-framework observations, and troubleshooting workflow. Use when Codex or another agent needs to explain 4GL constructs, generate or refactor X3 routines, review .src/.tra/.stc files, map help semantics into code, work with X3 object/GPOINT entry points, or troubleshoot runtime and authoring issues without inventing unsupported 4GL syntax.

Use the skill's own dictionary first. Use only bundled references under references/ at runtime; external project paths are build-time inputs only.

Read references/4gl-dictionary.md first for any symbol, command, type, function, runtime variable, or curated corpus-only construct lookup.
Read references/4gl-knowledge-map.md when you need the best bundled source page, thematic lookup, entry-point router, or version/canonicality guidance.
Read references/4gl-syntax.md when the task involves control flow, file structure, declarations, joins, transactions, event layout, or mask behavior.
Read references/4gl-patterns.md when you need realistic but sanitized project idioms derived from field code.
Read references/4gl-troubleshooting.md when debugging, linting, or reviewing suspicious runtime behavior.
Read references/4gl-precedence-and-validation.md if you need provenance rules or must judge conflicts between normative semantics and corpus habits.
Read references/4gl-refinement-report.md before promoting observed-only constructs into stronger guidance.

Prefer the dictionary's normalized entry over ad hoc guesses.
Prefer authoritative-knowledge entries over generic plugin/helper entries and over corpus-only observations.
If a symbol is absent from the dictionary and bundled knowledge map, say that the skill cannot confirm it instead of inventing syntax.
Do not open the original EnterScript project knowledge path during skill use; follow only links inside this skill.
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.

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.

The current generated dictionary contains 377 normalized entries across 10 categories, including 374 curated EnterScript 4GL symbol/concept pages.