Menu
Use when asked what XppAI skills are available or how to use the XppAI suite.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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-help |
| description | Use when asked what XppAI skills are available or how to use the XppAI suite. |
| Skill | Purpose |
|---|---|
xppai-init | Shared AX 2009 foundation — auto-loads on any X++ task |
xppai-explain | Understand unfamiliar methods, classes, forms, or tables |
xppai-exportxpo | Generate a ready-to-paste X++ job for exporting AOT objects to XPO files |
xppai-stack | Analyze profiler traces and stack traces |
xppai-codefix | Propose minimal, safe, production-ready code fixes |
xppai-architect | Review code for architectural weaknesses and design gaps |
xppai-posting | Analyze FormLetter posting flows and transactional behavior |
xppai-risk | Assess change risk before modifying any code |
xppai-support | Troubleshoot symptom-first AX 2009 support issues with a standard-first cause tree |
xppai-babysit | Static orchestrator — paste any artifact, get a full labeled analysis |
xppai-papai | Dynamic senior agent — reasons about what to apply and synthesizes findings |
xppai-report | Generate standardized markdown reports (change report, session resume, technical report) |
xppai-review | Final compliance gate for tags, localization protection, and AX 2009 output rules |
Don't know where to start? → xppai-babysit or xppai-papai
Reading unfamiliar code? → xppai-explain
About to change something? → xppai-risk
Something is slow? → xppai-stack
Posting flow is broken or unclear? → xppai-posting
Functional/support issue with no code yet? → xppai-papai (routes to xppai-support when appropriate)
Need a fix? → xppai-codefix
Something smells architecturally wrong? → xppai-architect
Need a formal report artifact? → xppai-report
Need to verify compliance before final output? → xppai-review
.xpo directly before analysis skillsTag ID terminology (not SPS-specific wording).Tag ID, Project ID, Dev Name, and current date (DD/MM/YYYY)..claude/ and generated reports/ output).