scriptrunner-platform-guidance

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use this skill whenever you need ScriptRunner platform operating rules.

每当需要了解 ScriptRunner 平台的操作规则时，请使用此 skill。

The user asks for ScriptRunner for Jira or Confluence implementation help on Cloud or Data Center.
The user asks for a Data Center to Cloud migration or conversion.
The task involves HAPI, Java APIs, REST APIs, Behaviours, workflow functions, listeners, CQL jobs, custom macros, scripted fields, or Dev and Deployment YAML.

用户请求 ScriptRunner 在 Jira 或 Confluence 的 Cloud 或 Data Center 环境中的实现帮助。
用户请求从 Data Center 迁移或转换到 Cloud。
任务涉及 HAPI、Java APIs、REST APIs、Behaviours、workflow functions、listeners、CQL jobs、custom macros、scripted fields，或 Dev and Deployment YAML。

Identify the source and target platforms and products.
Read
```
references/INDEX.md
```
.
Read the matching guidance file:
- ```
references/cloud.md
```
  for ScriptRunner for Jira Cloud.
- ```
references/confluence-cloud.md
```
  for ScriptRunner for Confluence Cloud.
- ```
references/data-center.md
```
  for ScriptRunner for Jira Data Center.
For Jira Data Center to Cloud migrations, read
```
references/data-center.md
```
and the target product's Cloud guidance before producing code: Data Center explains the source semantics, while the Jira or Confluence Cloud file explains the target constraints.
For Confluence Data Center to Cloud migrations, take the source semantics from the
```
scriptrunner-documentation
```
skill's
```
references/INDEX-CONFLUENCE-DATA-CENTER.md
```
and the target constraints from
```
references/confluence-cloud.md
```
before producing code. Confluence Data Center has no guidance file here, and
```
references/data-center.md
```
describes Jira Data Center only, so never apply it to a Confluence source.
Apply the guidance together with focused documentation, example, REST spec, and validator lookups.

确定源平台与目标平台及其对应产品。
阅读
```
references/INDEX.md
```
。
阅读匹配的指导文件：
- Jira Cloud 的 ScriptRunner 指导文件为
```
references/cloud.md
```
  。
- Confluence Cloud 的 ScriptRunner 指导文件为
```
references/confluence-cloud.md
```
  。
- Jira Data Center 的 ScriptRunner 指导文件为
```
references/data-center.md
```
  。
对于从 Jira Data Center 迁移到 Cloud 的任务，在编写代码前阅读
```
references/data-center.md
```
和目标产品的 Cloud 指导文件：Data Center 文件说明源平台的语义，而 Jira 或 Confluence Cloud 文件说明目标平台的限制。
对于从 Confluence Data Center 迁移到 Cloud 的任务，源平台语义来自
```
scriptrunner-documentation
```
skill 的
```
references/INDEX-CONFLUENCE-DATA-CENTER.md
```
，目标平台限制来自
```
references/confluence-cloud.md
```
，然后再编写代码。此处没有 Confluence Data Center 的指导文件，且
```
references/data-center.md
```
仅介绍 Jira Data Center，因此绝不能将其应用于 Confluence 源平台。
将这些指导与有针对性的文档、示例、REST spec 和 validator 查询结合使用。

Keep platform and product assumptions explicit.
The guidance files are intentionally complete prompt references. The full-read rule applies to platform guidance only, not product documentation, examples, or OpenAPI specs.
Skip any guidance file your system prompt already includes. Otherwise read the selected guidance file in full before producing code, running API lookups, or validating an answer, in as few reads as possible. Do not delegate this read to a subagent.

明确说明平台和产品方面的假设。
这些指导文件被有意设计为完整的 prompt 参考资料。完整阅读规则仅适用于平台指导，不适用于产品文档、示例或 OpenAPI specs。
如果系统 prompt 中已经包含某个指导文件，则跳过该文件。否则，在编写代码、执行 API 查询或验证答案之前，必须完整阅读选定的指导文件，并尽可能减少读取次数。不要将此阅读任务委托给 subagent。