تشغيل أي مهارة في Manus بنقرة واحدة

xppai-posting

النجوم٦

التفرعات٠

آخر تحديث١٩ مايو ٢٠٢٦ في ٠٠:٠٧

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.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

betaxD

betaxD/xppai

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	xppai-posting
description	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.

XppAI Posting

Required background: xppai-core + xppai-domain
XPO input: run xppai-intake once

Use canonical evidence labels: Confirmed | Likely | Hypothesis | Unknown.

Pre-condition Gate

Require posting-class code or FormLetter-related evidence. If not provided, stop and request the relevant posting artifact before analysis.

Output

Executive Summary
Posting Scenario
Entry Point and Main Framework Path
Standard Framework Behavior in Play
Customization Behavior Found
Key Side Effects and Generated Artifacts
Fragile or High-Risk Areas
What to Inspect Next
Safe-Change Notes

Adaptive Depth

Omit sections that would be empty, N/A, or filler.

المزيد من هذا المستودع

نفس المستودع

xppai-stack

betaxD/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.

2026-05-196

xppai-architect

betaxD/xppai

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.

2026-05-196

xppai-babysit

betaxD/xppai

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.

2026-05-196

xppai-codefix

betaxD/xppai

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.

2026-05-196

xppai-core

betaxD/xppai

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

2026-05-196

xppai-domain

betaxD/xppai

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

2026-05-196

name	xppai-posting
description	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.

XppAI Posting

Required background: xppai-core + xppai-domain
XPO input: run xppai-intake once

Use canonical evidence labels: Confirmed | Likely | Hypothesis | Unknown.

Pre-condition Gate

Require posting-class code or FormLetter-related evidence. If not provided, stop and request the relevant posting artifact before analysis.

Output

Executive Summary
Posting Scenario
Entry Point and Main Framework Path
Standard Framework Behavior in Play
Customization Behavior Found
Key Side Effects and Generated Artifacts
Fragile or High-Risk Areas
What to Inspect Next
Safe-Change Notes

Adaptive Depth

Omit sections that would be empty, N/A, or filler.