菜单
Use only when XPO input is present to run canonical intake once (detect XPO, choose direct evidence path, and set intake state).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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).
| name | xppai-intake |
| description | Use only when XPO input is present to run canonical intake once (detect XPO, choose direct evidence path, and set intake state). |
Canonical XPO intake policy. Run only when XPO input is present.
Treat input as XPO when either is present:
.xpoCLASS #, TABLE #, FORM #, QUERY #, MAP #, VIEW #, JOB #, PROJECT #.xpo directly and read only required object textXPO intake already completed for this requestWhen fallback is required, include:
Path used: fallbackFallback reason: <file access failure|missing detail> - <concrete detail>Otherwise include:
Path used: direct-file