菜单
Load when answering questions about the current Pega application -- app stats, workflows, case types, data objects. Uses get-application as the primary source before any rule-level exploration.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the bundled Pega Infinity Authoring Codex plugin needs setup, authentication help, or troubleshooting. Confirm the plugin MCP server first, then verify the bundled runtime and skills payload.
Use when the GitHub Copilot CLI plugin needs connection setup help, environment configuration, or troubleshooting. Guides first-time setup, OAuth configuration, and recovery from connection failures.
Use this skill when the user asks to design or review a data model, choose between Case Type vs. Data Object, model a business process in App Studio or Dev Studio, add or change Case Types or Data Objects, or structure fields, relationships, primary fields, business keys, or attachments within a Pega application.
Load before creating or updating any Pega rules. Covers the ChangeRequest 4-stage lifecycle (intake, authoring, review, complete), branch isolation, case properties, and resuming cases.
Load when building a DX API assignment action payload for runtime case updates. Covers when to use content, when to use pageInstructions, how to combine them, and how to structure supported page, page-list, and page-group instructions for perform-action.
General instructions for creating and updating Pega rules using the schema-backed authoring tools
| name | methodology-explain-application |
| description | Load when answering questions about the current Pega application -- app stats, workflows, case types, data objects. Uses get-application as the primary source before any rule-level exploration. |
Use get-application as the single primary source for application understanding questions.
Treat these as application-state requests:
When intent matches, do not start with search-rules or multiple get-rule calls.
| Situation | Action |
|---|---|
Both appName and appVersion known | Proceed to Step 2 |
| Neither known | Call get-application with no parameters (discovers default app) |
| Only one known | Ask for the missing value |
Tool: get-application
Parameters: appName, appVersion (both optional), detail="summary" (default)
The summary includes: application label/description, case types, lifecycle structures (stages/processes/steps), data objects, and personas.
Decision gate: If the payload answers the question, stop and respond. Only escalate if a specific requested field is missing.
| Section | Source fields |
|---|---|
| Application definition | pyDADInfo.pyLabel, pyDADInfo.pyDescription |
| Stats | Counts of pyCandidateCaseTypes[], pyCandidateDataObjects[], pyCandidatePersonas[] |
| Workflows | Case types → pyDCDInfo → pyCandidateStages[] → pyCandidateStageProcesses[] → pyCandidateStageSteps[] |
| Data objects | pyCandidateDataObjects[] → pyCandidateFields[] with types and references |
Use resolved labels (persona/object names), not raw GUIDs.
After the summary, ask whether the user wants:
| Rule | Guidance |
|---|---|
| Minimum-call | Start with exactly one get-application call |
| Stop condition | If payload contains the answer, stop tool-calling |
| Escalation condition | Only when a required detail is absent — state missing field(s) first |
| No over-fetching | Never fetch flows/rules "just in case" |
Use rule-level exploration only if:
get-application summary lacks a specific technical detailEscalation sequence:
search-rules to locate artifactsget-rule detail="summary" firstget-rule detail="full" only when raw fields requiredTo find the Pega platform version, search for Rule-RuleSet-Version rules named Pega-RULES.
The highest 08-XX-YY pattern maps to the Infinity release year: 08-24 = Infinity '24,
08-25 = Infinity '25. The patch (YY) indicates update level.
appName or only appVersion — provide both or neitherpyGUID, pxObjClass) unless debugging