xppai

Use when analyzing X++ AX 2009 profiler traces, code stack traces, or execution paths to identify performance bottlenecks — repeated call chains, quadratic loops, expensive constructor+calc combos, excessive tax/totals recalculation, or deep framework cascades.

Use when reviewing X++ or general ERP source code for architectural weaknesses, design gaps, fragile sequencing, responsibility mismatches, technical debt, or structural risks — not just syntax or performance issues.

Use when given any X++ AX 2009 artifact — stack trace, method, class, form XPO, posting code, or table — and you need a full structured multi-skill analysis applied automatically based on artifact type.

Use when proposing X++ AX 2009 code fixes for identified performance bottlenecks or behavioral bugs — minimal, production-safe changes that preserve business logic and fit ERP team review standards.

Use for all XppAI AX 2009 tasks as the canonical core baseline (architecture, language, lifecycle, hard constraints, and evidence labels).

Use when deep AX 2009 analysis is required (performance, posting, totals/tax, framework patterns, customization safety, and architecture judgment).

Use when reading unfamiliar X++ AX 2009 code — methods, classes, forms, tables, or XPO extracts — to understand what it does, what triggers it, what it calls, and where it fits in the AX execution model.

Use when asked what XppAI skills are available or how to use the XppAI suite.

Deprecated compatibility entry. Use xppai-core + xppai-domain (+ xppai-intake for XPO input) instead.

Use only when XPO input is present to run canonical intake once (detect XPO, choose direct evidence path, and set intake state).

Use when given any X++ AX 2009 artifact and you need an intelligent senior-engineer analysis — reads the artifact, reasons about what matters most, dynamically selects which skills to apply and in what order, and synthesizes findings into a practical assessment.

Use when analyzing AX 2009 posting flows, document generation, FormLetter classes, journal creation, or any transactional framework behavior involving SalesFormLetter, PurchFormLetter, totals, tax, inventory, or ledger posting.

Use when assessing how risky it is to modify X++ AX 2009 code before making changes — identifies callers, dependencies, regression surface, business flow impact, and safest change strategy.

Use when an AX 2009 issue starts as a business symptom or support error and you need a standard-first troubleshooting cause tree that can escalate to customization and XPO analysis when needed.

Use when reviewing X++ or general ERP source code for architectural weaknesses, design gaps, fragile sequencing, responsibility mismatches, technical debt, or structural risks — not just syntax or performance issues.

Use when given any X++ AX 2009 artifact — stack trace, method, class, form XPO, posting code, or table — and you need a full structured multi-skill analysis applied automatically based on artifact type.

Use when proposing X++ AX 2009 code fixes for identified performance bottlenecks or behavioral bugs — minimal, production-safe changes that preserve business logic and fit ERP team review standards.

Use when reading unfamiliar X++ AX 2009 code — methods, classes, forms, tables, or XPO extracts — to understand what it does, what triggers it, what it calls, and where it fits in the AX execution model.

Use when asked what XppAI skills are available or how to use the XppAI suite.

Use when working with any X++ AX 2009 code, analysis, review, or fix task — loads foundational AX 2009 and X++ knowledge required by all xppai skills.

Use when given any X++ AX 2009 artifact and you need an intelligent senior-engineer analysis — reads the artifact, reasons about what matters most, dynamically selects which skills to apply and in what order, and synthesizes findings into a practical assessment.

Use when analyzing AX 2009 posting flows, document generation, FormLetter classes, journal creation, or any transactional framework behavior involving SalesFormLetter, PurchFormLetter, totals, tax, inventory, or ledger posting.

Use when the user asks to generate AX 2009 analysis reports in markdown, especially change reports, session resume reports, or technical reports. Produces standardized output using XppAI report templates consistent with existing project report layout.

Use to validate XppAI outputs before final delivery, especially to enforce Tag ID block compliance and ensure no edits are proposed inside localization blocks (<GBR>, <GIN>, <GJP>, <GSA>, <GTH>).

Use when assessing how risky it is to modify X++ AX 2009 code before making changes — identifies callers, dependencies, regression surface, business flow impact, and safest change strategy.

Use when analyzing X++ AX 2009 profiler traces, code stack traces, or execution paths to identify performance bottlenecks — repeated call chains, quadratic loops, expensive constructor+calc combos, excessive tax/totals recalculation, or deep framework cascades.

Use when an AX 2009 issue starts as a business symptom or support error and you need a standard-first troubleshooting cause tree that can escalate to customization and XPO analysis when needed.

Use when you need to export a list of AX 2009 AOT objects to XPO files — generates a ready-to-paste X++ job given object names or full AOT paths.