メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | xppai-babysit |
| description | 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. |
Required background: xppai-core + xppai-domain
XPO input: run xppai-intake once
Detect artifact type and select sequence:
xppai-stack -> xppai-codefixxppai-explain -> xppai-posting -> xppai-risk -> xppai-codefixxppai-explain -> xppai-architect -> xppai-riskxppai-explain -> xppai-architect -> xppai-risk -> xppai-codefixxppai-explain -> xppai-risk -> xppai-codefixxppai-explain -> xppai-riskWhen multiple classes match, state ambiguity and chosen type explicitly.
Always emit:
## [ARTIFACT TYPE DETECTED: <type>]## [CLASSIFICATION CONFIDENCE: High|Medium|Low — <reason>]## [SKILLS APPLIED: ...]Default to Mode: brief for all invoked skills and provide one consolidated summary.
Add Full Analysis Available note with per-skill invocation guidance.
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 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.