@1aboveio/skills 0.0.0-stage → 1.0.0

package/skills/core/house-style/references/style-en.md

@@ -0,0 +1,131 @@
+# English style
+
+Sentence-level rules for English text. Apply them to every template in English or in the English
+version of a bilingual document. WRITING.md and the template override them
+([precedence](rules.md#resolve-conflicting-instructions)); language-neutral layout rules are in
+[defaults](defaults.md).
+
+Write so a busy expert understands on the first read.
+
+## Contents
+
+- [Three rules above the rest](#three-rules-above-the-rest)
+- [Voice](#voice)
+- [Sentences](#sentences)
+- [Instructions and procedures](#instructions-and-procedures)
+- [One reading only](#one-reading-only)
+- [Words](#words)
+- [Rhythm](#rhythm)
+- [Before and after](#before-and-after)
+
+## Three rules above the rest
+
+**Cut every word that does no work.** "In order to" is "to". "It should be noted that" is nothing.
+
+**Use the short everyday word.** "use" not "utilize", "help" not "facilitate", "start" not
+"commence", "about" not "approximately" in prose. A long word must buy its length with precision.
+
+**When a rule makes a sentence worse, fix the sentence another way.** A sentence that obeys every
+rule and reads like a machine wrote it has failed.
+
+## Voice
+
+**Lead with the point.** Open the document and each section with the conclusion, then the support.
+Example: "We recommend renewing with Vendor B. It meets all five requirements at the lowest cost."
+Not: "This section reviews the three vendors we considered."
+
+**Name who does what.** "Operations reviews each alert within one business day", not "Alerts are
+reviewed". Use passive only when the actor is unknown or irrelevant.
+
+**Address the reader as "you" and your organization as "we"**, unless WRITING.md names the parties
+otherwise ("the Client").
+
+**State findings plainly; hedge only real uncertainty, and say what it depends on.** "Losses will
+likely halve if the new rule's hit rate holds in production." Not: "This could potentially help
+reduce losses."
+
+**Have a view where the document allows one.** An analysis or recommendation says what the
+trade-offs add up to. A reference section or a policy statement stays neutral.
+
+## Sentences
+
+- One thought per sentence. Split a sentence that carries two; keep a long sentence that carries
+  one fact with its condition.
+- Most sentences under 25 words; instructions under 20.
+- Present tense for how things are. "Will" only for what happens later.
+- Put the common case first and exceptions after.
+- Write full sentences, not telegraphic notes. Keep the words that carry the logic: if,
+  when, because, but. Without them a rule becomes a label the reader has to decode.
+  Example: "It is 0 if there were no collections," not "0 when none."
+- Introduce a list with a complete sentence; keep list items parallel.
+- Use periods, not semicolons. Replace a dash aside with a new sentence.
+
+## Instructions and procedures
+
+- Write each step as a command with one action: "Open the alert." Not "The analyst should open the
+  alert", not "The alert is opened".
+- Put the condition or warning before the action it guards: "If the payee is on the list, stop the
+  payment." "To delete the case, select Delete."
+- Say what the reader should see after a step when it confirms success.
+- Never "simply", "just", "easy" or "quickly" in a procedure. If it were easy, the reader would not
+  be reading.
+- Never "please" in instructions.
+
+## One reading only
+
+- Keep "only" and "not" next to the word they limit: "fails only on retries" and "only fails on
+  retries" differ.
+- Break up noun stacks: "the merchant risk score threshold review process" → "the process that
+  reviews the threshold for merchant risk scores".
+- Make every "it", "this" and "they" point to one obvious noun. Repeat the noun when in doubt. Never
+  point "this" or "which" at a whole clause.
+- Keep "the", "a" and "that": "Remove the backup file", "Ensure that the switch is off".
+- Do not drop verbs: "Phase 1 moves the data and Phase 2 the reports" → "and Phase 2 moves the
+  reports".
+- No slashes: "a, b, or both", not "a/b" or "and/or". No "(s)" plurals. No "etc."; say up front
+  that a list is partial.
+- No idioms, metaphors or Latin abbreviations (e.g., i.e., viz.); write "for example", "that is".
+- Give every range its endpoints and say which are included: "from 00:00 up to, not including,
+  06:00", not "between midnight and 6".
+- When "and" and "or" meet in one condition, group them: "verified, and either a person or a
+  merchant", not "a person or a merchant and verified". Give each condition its own subject.
+- Define a term by when it applies, not by a synonym: "'undetermined' when the name matches no
+  rule", not "'undetermined' means it cannot be determined".
+
+## Words
+
+- **The system is the word list.** Write the real field, endpoint, report, product or form name in
+  its exact form, in code font when it is code. Not a synonym, not a description of it.
+- **One word, one meaning, one thing.** Pick "merchant" or "seller" and keep it. Do not use
+  "check" for both "inspect" and "restrain".
+- **Do not coin jargon.** Use the words a practitioner says aloud. Define a necessary term at first
+  use.
+- **Spell out an abbreviation at first use** unless the reader uses it daily (API, KYC, AML).
+- **Banned as filler**: leverage, robust, seamless, holistic, synergy, delve, streamline,
+  cutting-edge, best-in-class, world-class, "plays a pivotal role", "a testament to".
+
+## Rhythm
+
+Mix sentence lengths on purpose. Short sentences land a point; longer ones carry a fact with its
+condition or consequence. Be specific over sterile: not "schema changes can cause issues" but "a
+renamed column breaks the nightly export".
+
+## Before and after
+
+Before:
+
+> Configuration of the alert threshold parameters is performed via the rules console. It is
+> important to note that changes, which take effect immediately, should only be made after
+> approval. If not followed, audit findings may result.
+
+After:
+
+> Change alert thresholds in the rules console. A change takes effect immediately, so make it only
+> after the MLRO approves it. An unapproved change is an audit finding.
+
+## Sources
+
+Original text. Informed by the Google developer documentation style guide (CC BY 4.0), the
+ASD-STE100 Simplified Technical English principles, Global English guidance, and the layered
+approach in Cursor's `technical-writing` skill (github.com/cursor/plugins, no license stated;
+ideas only, no text copied). See [sources](sources.md).

package/skills/core/house-style/references/style-zh.md

@@ -0,0 +1,141 @@
+# 中文风格
+
+中文正文的句子与排版规则。用于任何模板的中文文档，或双语文档的中文版本。WRITING.md 和模板优先于本文件
+（[优先级](rules.md#resolve-conflicting-instructions)）；与语言无关的结构与版式规则见
+[defaults](defaults.md)。
+
+本文件以 [Fenng/tech-doc-style-chinese](https://github.com/Fenng/tech-doc-style-chinese)（MIT）为基础改编，版权与许可声明见文末。
+
+## 目录
+
+- [规则优先级](#规则优先级)
+- [事实保真](#事实保真)
+- [语义与语气](#语义与语气)
+- [结构与句子](#结构与句子)
+- [操作步骤与故障排查](#操作步骤与故障排查)
+- [术语与黑话](#术语与黑话)
+- [标点与留白](#标点与留白)
+- [简体与繁体](#简体与繁体)
+- [改写前后](#改写前后)
+
+## 规则优先级
+
+冲突时按以下顺序处理：
+
+1. 保留事实、逻辑、限制、安全信息和法律含义。
+2. 服从用户明确要求和项目约定（先后顺序见 [规则](rules.md#resolve-conflicting-instructions)）。
+3. 保持术语和机器可读内容准确。
+4. 改善结构、语义、语气和可扫读性。
+5. 最后处理标点、留白、大小写。
+
+不要为了句子更短、语气更确定或格式更统一而牺牲上一级的信息。
+
+## 事实保真
+
+- 不新增来源没有的日期、数字、时限、SLA、能力、条件、因果或结论。
+- 不删除前置条件、适用范围、例外、风险、安全警告和失败处理。
+- 不把「可能」「计划」「建议」「通常」改写成确定事实。
+- 信息不足时标记缺口（格式见 [缺口标记](rules.md#gap-markers)），不要自行补全。示例：`尽快处理` → `在约定时限内处理【待确认：处理时限，负责人：<文档负责人>】`；不要补成 `30 分钟内处理`。
+- 法规、合同、错误原文和用户提供的固定文案保持原样，建议另行列出。
+
+## 语义与语气
+
+- 准确先于修辞，清晰先于热闹。使用克制、直接、可执行的中文。
+- 先回答「是什么、适用于什么、需要做什么、接着看哪里」。
+- 不写问候式开场、宣传口号和空泛形容。
+- 技术文档默认不直接称呼读者，使用无主句或明确角色（开发者、实施人员、业务负责人）。WRITING.md 可改为「您」或「你」。
+- 一个段落承载一个主要信息点；段落源文件保持一段一行，不硬换行。
+
+## 结构与句子
+
+- 一个句子保持一个清晰主干，不连续堆叠条件、动作和例外。
+- 写完整的句子，不写电报体：保留表达逻辑的词，包括条件（若……则、当……时）、因果（因为、所以）和转折（但）。省掉这些词，规则就成了要读者自己解码的标签。示例：`若窗口内无收款，则为 0`，而不是 `无收款为 0`；`付款人名称为空的收款不计入`，而不是 `空值不计`。
+- 标题说明用途或结论，不只写抽象名词。示例：`退单量在调价后翻倍`，而不是 `分析`。
+- 列表项保持相同层级、句式和信息密度；完整句式的列表项统一加句号。
+- 指代可能不清时，用具体名称替代「该」「其」「此」「上述」「相关」。
+- 区间和阈值写明端点，并写明端点是否包含。示例：`北京时间 0:00（含）至 6:00（不含）`，而不是 `凌晨 0 点到 6 点之前`；`不低于 4,900 美元且低于 5,000 美元`，而不是 `比 5,000 美元低不到 2%`。
+- 名词前的修饰语超过两层时拆开：先写主干，再把限定条件前置为状语或另起一句。示例：`非平台收款笔数，只计币种为美元、欧元或英镑且不经合作银行的收款`，而不是 `累计以美元、欧元或英镑收到、且不经合作银行渠道的非平台收款笔数`。
+- 并列的条件逐个写全对象，不让后一个条件借用前一个条件的主语。「或」和「且」出现在同一个条件里时，用分句或列表写清每个连词管到哪里。示例：`客户已认证，且客户是个人或商户`，而不是 `客户是个人或商户且已认证`。
+- 解释一个词时，写出什么情况下得到它，不用同义词绕回去。示例：`若名称不匹配任何规则，则为「无法判定」`，而不是 `「无法判定」表示无法判断`。
+- 否定范围必须明确，读者能判断禁止的是哪个动作。
+- 区分系统自动行为和人工操作。示例：`选择「保存」。系统随后写入配置并重新加载服务。`
+
+## 操作步骤与故障排查
+
+用于操作手册、风险操作流程、故障排查和多步骤 API 调用，不用于叙述性文字和固定引用。
+
+- 一个步骤一个主要动作，以明确动作开头，写清动作对象；不只写「处理」「操作」「执行」。
+- 条件和风险放在动作之前。条件多时单独列出前置条件。不把关键限制放在步骤末尾的括号里。
+- 需要时写明每一步的预期结果，以及失败时的停止条件和恢复方式；来源没有的不补造。
+- 故障排查先给低风险、可逆、证据价值高的检查；写明判断条件；只有证据支持时才给出原因，不把「可能原因」写成「确定原因」。
+
+## 术语与黑话
+
+- 同一概念使用同一首选术语，不轮换同义词。先查项目的 TERMINOLOGY.md，再查[常用术语](terminology-zh.md)。
+- 缩写首次出现给出全称；产品名、机构名、代码、字段、命令保持官方写法。
+- 以下词语容易掩盖具体动作；除非有明确定义或引用原文，否则改写为实际含义：
+  赋能 → 提供；抓手 → 关键措施；闭环 → 完整流程，或写出开始、处理和完成条件；沉淀 → 形成、积累、保存；
+  对齐 → 统一、确认一致；拉通 / 打通 → 连接；洞察 → 分析结论；兜底 → 写出失败后的具体保障；
+  落盘 → 写入文件；透传 → 原样传给下游。
+- 以下词语依赖语境，不机械替换：场景、生态、体系、路径、触点、颗粒度、复盘、梳理、输出。
+- 不用装饰性连接词：值得注意的是、不难看出、综上所述、首先……其次……最后（非真实顺序时）。表达条件、因果、转折的连接词要保留（见[结构与句子](#结构与句子)）。
+
+## 标点与留白
+
+- 中文正文使用全角标点。引号默认用直角引号「」，嵌套用『』；WRITING.md 可改用 “”。
+- 按钮、菜单、字段展示名用「」；文档和作品名用《》；机器可读字段名用行内代码。
+- 中文说明用全角括号（），括号内侧不留空格；英文、代码中的括号保持原样。
+- 省略号用 `……`，破折号用 `——`。并列词语用顿号。
+- 中文与英文、数字、版本号之间加一个半角空格：`使用 API 获取数据`、`等待 3 秒`、`增长 50%`。数字与 `%`、单位符号之间不加空格。
+- 中文与行内代码之间加一个半角空格；紧邻中文标点时不加：``运行 `npm install`。``
+- 全角标点前后不加空格。不修改代码、链接目标、官方名称和用户指定的字面量。
+
+## 简体与繁体
+
+- 字形按简报指定，否则按 WRITING.md，否则与简报所用字形一致。全文统一，缺口标记和义务用语也一样：
+  - 简体：必须 / 不得 / 应当 / 可以；`【待确认：…，负责人：…】`
+  - 繁体：必須 / 不得 / 應當 / 可以；`【待確認：…，負責人：…】`
+- 地区用词跟随项目（如繁体港澳用语：「帳戶」「網站」「資料」），以 TERMINOLOGY.md 为准。
+
+## 改写前后
+
+改写前：
+
+`在开通商户之前需要确认商户已经完成了相关的尽职调查，然后由合规进行审批，审批通过后系统会自动开通。`
+
+改写后：
+
+1. `确认商户已完成客户尽职调查（CDD）。`
+2. `提交合规审批。`
+
+`审批通过后，系统自动开通商户。`
+
+检查点：条件在动作之前；区分人工动作和系统行为；「相关的」删除；术语使用 TERMINOLOGY.md 的首选词。
+
+## 版权与许可
+
+Portions adapted from tech-doc-style-chinese by Fenng (https://github.com/Fenng/tech-doc-style-chinese).
+
+```text
+MIT License
+
+Copyright (c) 2026 Fenng
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```

package/skills/core/house-style/references/terminology-zh.md

@@ -0,0 +1,223 @@
+# 常用中文术语
+
+Use this as the default word list for Chinese business, technical and payment writing. A project's own `TERMINOLOGY.md` wins wherever the two differ.
+Read the 繁體 column as Hong Kong usage, not Taiwan usage. `—` means no Hong Kong source was found.
+Look up each Source id in the [Sources](#sources) table at the end. These terms are guidance only: no script protects them.
+
+## Contents
+
+- [Translation-ese → natural Chinese](#translation-ese--natural-chinese)
+- [Technical and product terms](#technical-and-product-terms)
+- [Payment and risk](#payment-and-risk)
+- [Words to avoid in reports](#words-to-avoid-in-reports)
+- [Sources](#sources)
+
+## Translation-ese → natural Chinese
+
+Rewrite these patterns when they come from English sentence structure. The examples are illustrations, not fixed strings.
+
+| 避免 | 改为 | 说明 | Source |
+| --- | --- | --- | --- |
+| 对数据进行分析 | 分析数据 | Put the verb back instead of 进行/作出 + noun. | YU, SSPAI-1, SSPAI-2 |
+| 报告已被团队提交 | 团队已提交报告 | Use active voice and name the actor. 被 also sounds negative. | MS-TW, RUANYF, ZHSG, YU |
+| 当交易失败的时候，系统会重试 | 交易失败时，系统会重试 | Drop 当……的时候, or let time order carry it. | YU, SSPAI-1, GMRB |
+| 作为一名分析师，他负责周报 | 他是分析师，负责周报 | Keep subject and verb together. | SSPAI-1 |
+| 请检查你的账户的设置 | 请检查账户设置 | Drop possessives the context already gives. | MS-CN |
+| 团队的上月的报告的结论 | 团队上月报告的结论 | More than three 的 in a sentence: cut or split. | MS-CN, SIGUO, GMRB |
+| 过去三个月由商户提交但尚未处理的退款申请已全部关闭 | 商户过去三个月提交的退款申请，凡未处理的都已关闭 | Split a long modifier into its own clause, main point first. | MS-CN, ZHSG, RUANYF |
+| 所有商户们都已完成审查 | 所有商户都已完成审查 | Drop 们 when a number, 都 or 所有 already marks the plural. | YU, SSPAI-1, RUANYF |
+| 关于费率的调整已经生效 | 费率调整已经生效 | Most 关于/有关 can just go. | YU |
+| 这份报告的可读性很差 | 这份报告很难读 | Use the plain verb or adjective instead of a noun with 性. | YU |
+| 这是一个有用的功能 | 这个功能很有用 | Translate an English article only when it prevents confusion. | MS-CN |
+| 5 个交易 | 5 笔交易 | Use the specific measure word, not 个. | MS-CN, MS-TW |
+| 欺诈是主要风险之一 | 主要风险是欺诈和套现 | Name the members or the count instead of ……之一. | SSPAI-1 |
+| 拒绝率上升，部分原因在于规则过严 | 拒绝率上升，有一个原因是规则过严 | Avoid the stock 部分原因在于. | SSPAI-1 |
+| 比如 Visa、万事达卡 | Visa、万事达卡等 | Close an example list with 等. | SSPAI-1 |
+| 针对小商户的费率 | 适用于小商户的费率 | Use 适用于 when *for* means who it applies to. | MS-CN |
+| 将文件上传至服务器 | 将文件上传到服务器 | Plain register prefers 到 over 至. | MS-CN, MS-TW |
+| 倘若交易失败 | 如果交易失败 | Use 如果 in reports. 倘若 and 假使 read stiff. | MS-CN |
+| 若要导出报告，请打开菜单 | 要导出报告，请打开菜单 | Use 要 instead of 若要. | MS-CN |
+| 上传中…… | 正在上传…… | Use 正在 for an action in progress. Headings stay as they are. | MS-CN |
+| 列名称、文件名称 | 列名、文件名 | In Simplified, drop 称 from compound names. | MS-CN, WP-IT |
+| 全部 5 条规则都已成功启用 | 5 条规则都已启用 | 都 already means all. Drop the extra 全部 and 成功. | MS-CN |
+| 没有导出权限的用户无法导出报告 | 用户需要导出权限才能导出报告 | State the rule positively instead of as a double negative. | RUANYF |
+
+## Technical and product terms
+
+Use the Hong Kong form in the 繁體 column even where Microsoft's Traditional list gives the Taiwan form.
+A `（港）` note in Avoid marks a Taiwan form that Hong Kong text should not use.
+
+| Concept | English | 简体 | 繁體 | Avoid | Meaning | Source |
+| --- | --- | --- | --- | --- | --- | --- |
+| Sign-in identity | account | 账号 | 帳戶 | 帳號（港） | The identity a person signs in with; not a money account. | WP-IT, MS-HK |
+| Data | data | 数据 | 數據 | 資料（港，指 data 时） | Recorded values or records; in Hong Kong 資料 means information instead. | MS-TERM, WP-IT, HKMA-AML |
+| Information | information | 信息 | 資料 |  | Facts given or received, as in customer information; not raw data. | MS-TERM, HKMA-AML |
+| Database | database | 数据库 | 資料庫 |  | A structured store of data managed by software; 數據庫 is also seen in Hong Kong. | MS-TERM, WP-IT, MS-HK |
+| Default | default | 默认 | 預設 | 缺省 | The value used when nobody sets one. | MS-TERM, WP-IT |
+| Computer file | file | 文件 | 檔案 |  | A file on disk; in Traditional Chinese 文件 means a document instead. | MS-TERM, WP-IT |
+| Document | document | 文档 | 文件 | 文件（简体，指 document 时） | A written document; Simplified keeps 文档 so that 文件 can mean a computer file. | MS-TERM, HKMA-AML |
+| Folder | folder | 文件夹 | 資料夾 |  | A container for files. | MS-TERM, WP-IT |
+| Network | network | 网络 | 網絡 | 網路（港） | Connected systems or devices; 網路 is the Taiwan form. | MS-TERM, WP-IT, HKMA-AML |
+| Internet | Internet | 互联网 | 互聯網 | 網際網路（港） | The public Internet. | WP-IT |
+| User | user | 用户 | 用戶 | 使用者（港） | A person who uses a product; 使用者 is the Taiwan form. | MS-TERM, WP-IT |
+| Username | username | 用户名 | 用戶名 | 用户名称 | The sign-in name of a user. | WP-IT, MS-CN |
+| Customer | customer | 客户 | 客戶 |  | A person or business that buys from or holds an account with the firm. | MS-TERM, PBOC-CDD |
+| Configuration | configuration | 配置 | 設定 |  | How a system is set up, usually in files or code. | MS-TERM, WP-IT |
+| Settings | settings | 设置 | 設置 |  | The options a user changes in a product's interface. | MS-TERM, WP-IT |
+| Technical threshold | threshold | 阈值 | 閾值 |  | A cut-off value in a rule or model; a regulatory amount is 规定金额 instead. | MS-TERM |
+| Dashboard | dashboard | 仪表板 | 儀表板 |  | A screen of key metrics. | MS-TERM |
+| Workflow | workflow | 工作流 | 工作流程 |  | A defined sequence of steps. | MS-TERM |
+| Rule | rule | 规则 | 規則 |  | A condition that triggers an action, such as a risk rule. | MS-TERM |
+| Software policy | policy | 策略 | 原則 |  | A product setting that enforces behavior; a business policy is 政策. | MS-TERM |
+| Review of a document or code | review | 评审 | 檢閱 |  | Reading a document or change to judge it; a periodic control review is 审查. | MS-TERM |
+| Decline | decline | 拒绝 | 拒絕 |  | Refusing a request; a refused card authorization is 授权拒绝, not a chargeback. | MS-TERM |
+| Report | report | 报告、报表（表格） | 報告、報表（表格） |  | A written account of findings; 报表 only for a tabular report. | MS-TERM |
+| Event log | log | 日志 | 紀錄檔 |  | A system's running record of events. | MS-TERM, WP-IT |
+| Record | record | 记录 | 記錄 |  | One entry in a table or log. | MS-TERM |
+| Query | query | 查询 | 查詢 |  | A request for data. | MS-TERM |
+| Sign in | sign in | 登录 | 登入 | 登陆 | Entering credentials to start a session; 登陆 means landing ashore. | MS-TERM, WP-IT, ZHSG |
+| Password | password | 密码 | 密碼 |  | A secret used to sign in. | MS-TERM |
+| Authentication | authentication | 身份验证 | 身份驗證 | 鉴权（指用户或持卡人身份验证时） | Proving who a user or cardholder is (3DS is cardholder authentication); 鉴权 is engineering jargon for API authorization. | MS-TERM |
+| Verification | verification | 验证 | 驗證 |  | Checking that something is correct or genuine. | MS-TERM |
+| Permission | permission | 权限 | 權限 |  | What a user is allowed to do. | MS-TERM |
+| Administrator | administrator | 管理员 | 管理員 |  | A user who manages a system and its users. | MS-TERM |
+| Alert | alert | 警报 | 警示 |  | A signal that needs attention, such as a risk alert. | MS-TERM |
+| Filter | filter | 筛选 | 篩選 |  | Narrowing a list by conditions. | MS-TERM |
+| Data field | field | 字段 | 欄位 |  | One named column or attribute in a record. | MS-TERM, WP-IT |
+| Batch | batch | 批量 | 批次 |  | Many items processed together. | MS-TERM, WP-IT |
+| Real-time | real-time | 实时 | 即時 |  | Happening as events occur, without a batch delay. | MS-TERM, WP-IT |
+| Metric | metric | 指标 | 指標 | 衡量標準（指 metric 时） | A measured quantity that tracks performance; 衡量標準 means a criterion. | MS-TERM |
+| Insight | insight | 见解 | 見解 | 洞察 | A finding that explains something; state the finding itself where possible. | MS-TERM |
+| Transaction | transaction | 交易 | 交易 | 事务（非数据库语境） | A business or payment transaction; 事务 only for a database transaction. | MS-TERM |
+| Payment | payment | 付款 | 付款 |  | Money paid for goods or services. | MS-TERM |
+| Server | server | 服务器 | 伺服器 |  | A computer that provides a service to others. | MS-TERM, WP-IT |
+| Software | software | 软件 | 軟件 | 軟體（港） | Programs; 軟體 is the Taiwan form. | MS-TERM, WP-IT |
+| Hardware | hardware | 硬件 | 硬件 | 硬體（港） | Physical equipment; 硬體 is the Taiwan form. | MS-TERM, WP-IT |
+| Template | template | 模板 | 模板 |  | A reusable starting layout. | MS-TERM, WP-IT |
+| Upload | upload | 上传 | 上載 | 上傳（港） | Sending a file to a server; 上傳 is the Taiwan form. | WP-IT, MS-TERM |
+| Download | download | 下载 | 下載 |  | Fetching a file from a server. | WP-IT, MS-TERM |
+| Message | message | 消息 | 訊息 |  | A piece of communication shown or sent to a user. | MS-TERM, WP-IT |
+| Link | link | 链接 | 連結 |  | A reference that opens another page or item. | MS-TERM, WP-IT |
+| Support | support | 支持 | 支援 |  | Being able to handle something, or help given to users. | MS-TERM, WP-IT |
+| Save | save | 保存 | 儲存 |  | Writing changes so they persist. | MS-TERM, WP-IT |
+| Search | search | 搜索 | 搜尋 |  | Looking for items by keyword. | MS-TERM, WP-IT |
+| Cache | cache | 缓存 | 快取 |  | A temporary copy kept for speed. | MS-TERM, WP-IT |
+| Cloud | cloud | 云 | 雲端 |  | Computing services run by a provider over the Internet. | MS-TERM |
+| Enable | enable | 启用 | 啟用 |  | Turning a feature on. | MS-TERM |
+| Disable | disable | 禁用 | 停用 |  | Turning a feature off. | MS-TERM |
+| Release | release | 版本、发布（指动作时） | 版本、發行（指動作時） |  | A shipped version, or the act of shipping it. | MS-TERM |
+| Privacy | privacy | 隐私 | 私隱 |  | Control over personal information. | MS-TERM |
+| Text message | SMS | 短信 | 短訊 |  | A mobile text message. | WP-IT |
+| Mobile app | mobile app | 移动应用 | 流動應用程式 |  | An application for phones and tablets. | WP-IT, HK-1823 |
+
+## Payment and risk
+
+Keep scheme codes and brand names in their official form: `TC40`, `SAFE`, `3DS`, `MCC`.
+Write out a Chinese gloss once, on first use, when readers may not know the code.
+
+| Concept | English | 简体 | 繁體 | Avoid | Meaning | Source |
+| --- | --- | --- | --- | --- | --- | --- |
+| Acquirer | acquirer | 收单机构 | 收單機構 |  | The bank or licensed payment institution that accepts card payments for merchants. | PBOC-ACQ, HSB-CB, VISA-HK |
+| Issuer | issuer | 发卡机构 | 發卡機構 |  | The bank or institution that issued the card. | PBOC-ACQ, PBOC-CLR, VISA-HK, HSB-CB |
+| Merchant | merchant | 商户 | 商戶 | 商家 | A business that accepts card payments; regulations call it 特约商户. | PBOC-ACQ, VISA-HK, MS-TERM |
+| Card scheme | card scheme | 卡组织、银行卡清算机构（法规） | 卡組織 |  | The network that runs card clearing, such as Visa or UnionPay. | PBOC-CLR, HSB-CB |
+| Cardholder | cardholder | 持卡人 | 持卡人 |  | The person the card was issued to. | PBOC-ACQ, VISA-HK |
+| Debit card | debit card | 借记卡 | 扣賬卡 | 支票卡、借記卡（港）、轉帳卡（港） | A card that draws on the holder's bank account. | HSB-CB, MS-TERM |
+| Approval | approve | 批准、授权成功（卡交易） | 批核 |  | Saying yes to a request; for a card transaction, the issuer's authorization approval. | MS-TERM, VISA-HK |
+| Clearing | clearing | 清算 | 結算 |  | The inter-institution step the scheme runs to process and reconcile transactions; Hong Kong calls it 結算. | PBOC-CLR, HKMA-GL |
+| Settlement | settlement | 结算 | 交收 | 清算（指付款给商户时） | Moving the funds, including paying the merchant; not the clearing step. Hong Kong calls it 交收. | PBOC-ACQ, PBOC-CLR, UP-AGR, MS-TERM, HKMA-GL |
+| Settlement account | settlement account | 结算账户 | — | 清算账户（指商户账户时） | The merchant's bank account that receives settled funds. | PBOC-ACQ, UP-AGR |
+| Money account | account | 账户 | 帳戶 | 帐户（简体） | An account holding money at a bank or payment institution; Hong Kong speech also says 戶口. | PBOC-ACQ, PBOC-CDD, HKMA-AML, MS-TERM |
+| Refund | refund | 退款、退货（银联交易类型） | 退款 |  | The merchant returning money to the cardholder; not a chargeback. | PBOC-ACQ, UP-AGR, HSB-CB |
+| Chargeback | chargeback | 拒付 | 退款要求 | 退款（指拒付时） | A cardholder dispute, raised through the issuer, that reverses a settled sale; UnionPay contexts say 退单. | UP-AGR, PP-CB, HSB-CB, MS-TERM |
+| Dispute | dispute | 争议 | 爭議 |  | A cardholder's challenge to a transaction; PBOC rules call the process 差错和争议处理. | PBOC-ACQ, HSB-CB |
+| Retrieval request | retrieval request | 调单 | — |  | The issuer asking the acquirer for the transaction record. | PBOC-ACQ, PP-CB |
+| Representment | representment | 再请款 | — |  | The merchant contesting a chargeback with evidence. | UP-AGR, PP-CB |
+| Pre-arbitration | pre-arbitration | 预仲裁 | — |  | The last exchange between issuer and acquirer before the scheme rules. | PP-CB |
+| Arbitration | arbitration | 仲裁 | 仲裁 |  | The scheme deciding a dispute the two sides could not settle. | PP-CB, HSB-CB |
+| Merchant category code | MCC | MCC | MCC |  | The four-digit code for a merchant's line of business, 商户类别码 on first use. | SAFE-MCC, PBOC-ACQ |
+| 3-D Secure | 3DS | 3DS | 3DS |  | The cardholder authentication step for online card payments; Visa's version is Visa Secure. | VISA-HK |
+| Card-not-present | card-not-present | 无卡交易 | — |  | A card payment made without the physical card, such as online. | PBOC-ACQ, VISA-HK |
+| Fraud | fraud | 欺诈 | 欺詐 | 诈骗（指卡欺诈时） | Unauthorized or deceptive use of a payment; 诈骗 is the word for criminal scams. | PBOC-ACQ, VISA-HK, SPC-2CARD |
+| Suspected fraud | suspected fraud | 疑似欺诈 | — |  | A transaction flagged as possibly fraudulent, not yet confirmed. | PBOC-ACQ |
+| Card cash-out | cash-out | 套现 | — |  | Turning a credit line into cash through fake or inflated sales. | PBOC-ACQ |
+| Terminal relocation | terminal relocation | 移机 | — |  | Moving a POS terminal away from its registered merchant site. | PBOC-ACQ |
+| Visa fraud report | TC40 | TC40 | TC40 |  | The issuer's fraud report to Visa, counted in VAMP with TC15 disputes. | VISA-VAMP |
+| Mastercard fraud report | SAFE | SAFE | SAFE |  | Mastercard's issuer fraud report, now the Fraud and Loss Database. | MC-FLD |
+| Mule account | mule account | 涉诈账户 | 傀儡戶口 | 钱骡 | An account used to receive and move criminal proceeds for someone else. | SPC-2CARD, HKU-GL |
+| Account seller | card seller | 卡农 | — |  | A person who sells or rents out their bank or payment account. | SPC-2CARD |
+| Rented-account laundering | — | 跑分 | — |  | Moving illicit funds through rented accounts for a fee. | SPC-2CARD |
+| Know your customer | KYC | 了解你的客户 | 認識你的客戶 |  | The principle of knowing who a customer is and what they do. | PBOC-CDD, HKMA-AML |
+| Customer due diligence | CDD | 客户尽职调查 | 客戶盡職審查 | 客户尽职审查（简体） | Identifying and verifying a customer and understanding their business. | PBOC-CDD, HKMA-AML |
+| Enhanced due diligence | EDD | 强化尽职调查 | 強化客戶盡職審查 |  | Extra checks for higher-risk customers. | PBOC-CDD, HKMA-AML |
+| Simplified due diligence | SDD | 简化尽职调查 | 簡化客戶盡職審查 |  | Lighter checks allowed for lower-risk customers. | PBOC-CDD, HKMA-AML |
+| Ongoing monitoring | ongoing monitoring | 持续的尽职调查 | 持續監察 |  | Keeping customer information and activity under review after onboarding. | PBOC-CDD, HKMA-AML |
+| Beneficial owner | beneficial owner | 受益所有人 | 實益擁有人 |  | The person who ultimately owns or controls a customer. | PBOC-CDD, AML-LAW, HKMA-AML |
+| Politically exposed person | PEP | 外国政要 | 政治人物 |  | A person with a prominent public role; mainland rules cover foreign officials. | PBOC-CDD, HKMA-AML |
+| Anti-money laundering | AML | 反洗钱 | 打擊洗錢 |  | Controls that stop criminal proceeds entering the financial system. | PBOC-ACQ, PBOC-CDD, HKMA-AML |
+| Counter-terrorist financing | CFT | 反恐怖融资 | 打擊恐怖分子資金籌集 |  | Controls that stop funds reaching terrorists. | PBOC-CDD, HKMA-AML |
+| Suspicious transaction report | STR | 可疑交易报告 | 可疑交易報告 |  | A report filed with the authority about a transaction that may involve crime. | PBOC-CDD, HKMA-AML |
+| Sanctions screening | sanctions screening | 名单核查 | 制裁篩查 |  | Checking customers against sanctions and terrorist lists. | AML-LAW, HKMA-AML |
+| Risk-based approach | risk-based approach | 基于风险的尽职调查措施 | 風險為本的方法 |  | Scaling checks to each customer's risk. | PBOC-CDD, HKMA-AML |
+| Correspondent banking | correspondent banking | 代理行 | 代理銀行 |  | One bank providing accounts and services to another bank. | PBOC-CDD, HKMA-AML |
+| Regulatory threshold | threshold | 规定金额 | 門檻 | 阈值（法规语境） | The amount at which a rule applies; a model or rule cut-off is 阈值. | PBOC-CDD, HKMA-AML |
+| Periodic review | review | 审查 | 覆核 |  | A scheduled control check of a customer or process; not a document review. | PBOC-CDD, HKMA-AML |
+
+## Words to avoid in reports
+
+An empty 简体 or 繁體 cell means: delete the word, or replace it with the specific fact, number or comparison.
+
+| Concept | English | 简体 | 繁體 | Avoid | Meaning | Source |
+| --- | --- | --- | --- | --- | --- | --- |
+| Superlative praise | best, most advanced |  |  | 最佳、最好、最先进、最高水平 | Name what is compared and give the number instead. | XINHUA, ZHSG, MS-CN |
+| Unsupported "only" | only, unique |  |  | 唯一（无依据时）、唯二 | Claim uniqueness only with evidence, and do not coin forms like 唯二. | MS-CN, RUANYF, ZHSG |
+| Vague degree | much better, basically |  |  | 很好地、较多、较好、完全地、基本地、事实上 | Replace the degree word with the number or an example. | ZHSG |
+| Vague quantity | some, many, nearly |  |  | 有些、大量、一些、少许、几乎、数倍 | Give the count, range or multiple. | ZHSG |
+| N-fold decrease | N times less | 降低了 N% | 降低了 N% | 降低 N 倍、减少 N 倍 | A decrease is a percentage; note 增加了两倍 means three times the original. | ZHSG |
+| Slang and internet abbreviations | slang |  |  | NB、TMD、哇噻 | Use the standard written word. | XINHUA, ZHSG |
+| Rhetorical question | rhetorical question |  |  | 难道……吗 | State the point as a plain sentence. | ZHSG, SSPAI-1 |
+| Exclamation | exclamation |  |  | ！（非警示） | Use an exclamation mark only to warn about an irreversible action. | ZHSG |
+| Over-casual address | casual tone |  |  | 亲爱的 | Write in a neutral, objective register. | RUANYF, ZHSG |
+
+## Sources
+
+| id | Source | URL | License |
+| --- | --- | --- | --- |
+| MS-CN | Microsoft Chinese (Simplified) Localization Style Guide | https://download.microsoft.com/download/1/5/9/159cb91c-b61b-4385-97ca-80ccc7ff1fa0/zho-chn-StyleGuide.pdf | © Microsoft; ideas and short term pairs only |
+| MS-TW | Microsoft Chinese (Traditional) Localization Style Guide | https://download.microsoft.com/download/2/9/3/293e6d41-ba40-451b-a41e-94bdb6242ae3/zho-twn-StyleGuide.pdf | © Microsoft; ideas and short term pairs only |
+| MS-TERM | Microsoft Terminology collection | https://learn.microsoft.com/en-us/globalization/reference/microsoft-terminology | Microsoft terms of use; terms only |
+| WP-IT | Chinese Wikipedia conversion group Module:CGroup/IT | https://zh.wikipedia.org/wiki/Module:CGroup/IT | CC BY-SA 4.0; term pairs only |
+| RUANYF | 阮一峰《中文技术文档的写作规范》 | https://github.com/ruanyf/document-style-guide/blob/master/docs/text.md | Public domain |
+| ZHSG | yikeke《中文技术文档写作风格指南》 | https://github.com/yikeke/zh-style-guide/tree/master/source | MIT |
+| SSPAI-1 | 葛仲君《地道中文怎么写？英中翻译要避免哪些坑？》少数派 | https://sspai.com/post/59943 | © 少数派; ideas only |
+| SSPAI-2 | PlatyHsu《不要逃避解释：论「相关」和「有关」在日常写作中的滥用》少数派 | https://sspai.com/post/98169 | © 少数派; ideas only |
+| YU | 余光中《怎样改进英式中文？》, via a chapter digest | https://vocus.cc/article/660f6ceafd89780001edf5e0 | © estate; ideas only |
+| SIGUO | 思果《翻译研究》, via reader excerpts | https://book.douban.com/subject/30155966/ | © publisher; ideas only |
+| GMRB | 于德英, 光明日报 2021 | https://www.chinawriter.com.cn/n1/2021/1027/c431803-32265433.html | © 光明日报; ideas only |
+| XINHUA | 《新华社新闻信息报道中的禁用词和慎用词》 | https://wdxy.jsu.edu.cn/upload/9E9D04CE60720572651241DEBB5_17BC5311_4AFCF.pdf | Newsroom rule; ideas only |
+| PBOC-ACQ | 《银行卡收单业务管理办法》 | https://www.gov.cn/gongbao/content/2013/content_2489981.htm | Regulation; not protected |
+| PBOC-CLR | 《银行卡清算机构管理办法》 | https://www.gov.cn/gongbao/2025/issue_12086/202506/content_7026998.html | Regulation; not protected |
+| PBOC-CDD | 《金融机构客户尽职调查和客户身份资料及交易记录保存管理办法》 | https://www.pbc.gov.cn/tiaofasi/144941/144957/4460304/index.html | Regulation; not protected |
+| AML-LAW | 《中华人民共和国反洗钱法》 | http://www.npc.gov.cn/npc/c2/c30834/202411/t20241108_440887.html | Statute; not protected |
+| SPC-2CARD | 两高一部《关于办理帮助信息网络犯罪活动等刑事案件有关问题的意见》 | https://www.court.gov.cn/zixun/xiangqing/472121.html | Judicial document; not protected |
+| SAFE-MCC | 国家外汇管理局《关于更新境内银行卡在境外使用的商户类别码分类的通知》 | http://m.safe.gov.cn/safe/2024/0322/24135.html | Official document; not protected |
+| UP-AGR | 中国银联《银联全渠道商户入网协议》 | https://open.unionpay.com/upload/download/%E9%93%B6%E8%81%94%E5%85%A8%E6%B8%A0%E9%81%93%E5%95%86%E6%88%B7%E5%85%A5%E7%BD%91%E5%8D%8F%E8%AE%AE-pdf%E7%89%88V1.2.pdf | © 中国银联; terms only |
+| HKMA-AML | 香港金融管理局《打擊洗錢及恐怖分子資金籌集指引（認可機構適用）》 | https://www.hkma.gov.hk/media/chi/doc/key-information/guidelines-and-circular/guideline/g33marked.pdf | © HKMA; terms only |
+| VISA-HK | Visa 香港 Visa Secure 商戶頁 | https://hk.review.visa.com/zh_HK/run-your-business/small-business-tools/payment-technology/visa-secure.html | © Visa; terms only |
+| HSB-CB | 恒生銀行 信用卡/扣賬卡退款保障機制資料 | https://www.hangseng.com/content/dam/hase/config/personal/cards/pdfs/zh_HK/chargeback_info.pdf | © Hang Seng Bank; terms only |
+| VISA-VAMP | Visa Acquirer Monitoring Program Fact Sheet | https://corporate.visa.com/content/dam/VCOM/corporate/visa-perspectives/security-and-trust/documents/visa-acquirer-monitoring-program-fact-sheet-2025.pdf | © Visa; facts only |
+| MC-FLD | Mastercard Developers, Fraud and Loss Database | https://developer.mastercard.com/fld-fraud-submission/documentation/use-cases/ | © Mastercard; facts only |
+| PP-CB | PingPong 收单 API 文档「拒付」术语页 | https://acquirer-api-docs-v4.pingpongx.com/notes/zh/technicalterm/chargebacks/ | © PingPong; terms only, industry usage |
+| HKU-GL | 香港大學 interpreting glossary | https://www.interpreting.hku.hk/glossary/?p=80026 | No licence stated; terms only |
+| HKMA-GL | 香港金融管理局《貨幣及銀行用語》結算與交收詞條 | https://www.hkma.gov.hk/media/chi/publications-and-research/reference-materials/monetary-and-banking-terms/12_index_eng.pdf | © HKMA; terms only |
+| MS-HK | Microsoft 香港中文支援與學習頁面 | https://support.microsoft.com/zh-hk/windows/security/identity-signin/manage-user-accounts-in-windows | © Microsoft; terms only |
+| HK-1823 | 香港政府 1823 流動應用程式頁面 | https://www.1823.gov.hk/tc/page/detail/1234 | © HKSAR Government; terms only |
+
+License limits:
+
+- WP-IT (CC BY-SA 4.0): this file uses single term pairs only. Do not import the conversion table, which would need attribution and share-alike.
+- ZHSG (MIT): nothing here is copied from it. Anything copied later must carry its MIT notice.
+- RUANYF is public domain. Nothing here is copied from it.
+- Regulator and court texts (PBOC-ACQ, PBOC-CLR, PBOC-CDD, AML-LAW, SPC-2CARD, SAFE-MCC) are not protected by copyright under PRC Copyright Law art. 5.
+- Microsoft, Visa, Mastercard, UnionPay, HKMA, Hang Seng, PingPong and HKU sources supply term pairs and facts only. Do not copy their sentences.
+- YU, SIGUO, SSPAI-1, SSPAI-2, GMRB and XINHUA supply ideas only. Every example in this file is newly written.

package/skills/core/house-style/release-check.mjs

@@ -0,0 +1,93 @@
+#!/usr/bin/env node
+import { spawnSync } from 'node:child_process';
+import { mkdirSync, readFileSync, writeFileSync } from 'node:fs';
+import { homedir } from 'node:os';
+import { dirname, join } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const DAY_MS = 24 * 60 * 60 * 1000;
+const WEEK_MS = 7 * DAY_MS;
+const here = dirname(fileURLToPath(import.meta.url));
+
+function readJson(path, fallback = {}) {
+  try { return JSON.parse(readFileSync(path, 'utf8')); } catch { return fallback; }
+}
+
+function frontmatterValue(text, key) {
+  const frontmatter = /^---\n([\s\S]*?)\n---/.exec(text)?.[1] ?? '';
+  const match = new RegExp('^' + key + ':\\s*([^\\n]+)$', 'm').exec(frontmatter);
+  return match?.[1].trim().replace(/^['"]|['"]$/g, '') ?? null;
+}
+
+function repositoryOf(source) {
+  const value = String(source ?? '').trim();
+  const match = /^(?:git@github\.com:|https:\/\/github\.com\/)?([A-Za-z0-9_.-]+\/[A-Za-z0-9_.-]+?)(?:\.git)?$/.exec(value);
+  return match?.[1] ?? null;
+}
+
+function stableVersion(value) {
+  const match = /^v?(\d+)\.(\d+)\.(\d+)$/.exec(String(value ?? '').trim());
+  return match ? match.slice(1).map(Number) : null;
+}
+
+function newer(left, right) {
+  for (let index = 0; index < 3; index += 1) {
+    if (left[index] !== right[index]) return left[index] > right[index];
+  }
+  return false;
+}
+
+function writeCache(path, value) {
+  try {
+    mkdirSync(dirname(path), { recursive: true });
+    writeFileSync(path, JSON.stringify(value));
+  } catch { /* A read-only cache must not block skill use. */ }
+}
+
+function main(now = Date.now()) {
+  if (process.env.ONEABOVEIO_NO_UPDATE_CHECK) return;
+  const skill = readFileSync(join(here, 'SKILL.md'), 'utf8');
+  const name = frontmatterValue(skill, 'name');
+  const localVersion = stableVersion(frontmatterValue(skill, 'release-version'));
+  if (!name || !localVersion) return;
+
+  const lock = readJson(join(process.env.HOME || homedir(), '.agents', '.skill-lock.json'));
+  const entry = lock.skills?.[name];
+  const repository = repositoryOf(entry?.sourceUrl || entry?.source);
+  if (!repository) return;
+
+  const cacheRoot = process.env.XDG_CACHE_HOME || join(process.env.HOME || homedir(), '.cache');
+  const cachePath = join(cacheRoot, '1aboveio-skills', 'release-check.json');
+  const all = readJson(cachePath);
+  const cache = all[repository] && typeof all[repository] === 'object' ? all[repository] : {};
+
+  if (!cache.lastCheck || now - cache.lastCheck >= DAY_MS) {
+    const result = spawnSync('gh', ['api', 'repos/' + repository + '/releases/latest', '--jq', '.tag_name'], {
+      encoding: 'utf8',
+      stdio: ['ignore', 'pipe', 'ignore'],
+      timeout: 1500,
+    });
+    cache.lastCheck = now;
+    if (result.status === 0 && stableVersion(result.stdout)) cache.latestTag = result.stdout.trim();
+    else delete cache.latestTag;
+    all[repository] = cache;
+    writeCache(cachePath, all);
+  }
+
+  const latestVersion = stableVersion(cache.latestTag);
+  if (!latestVersion || !newer(latestVersion, localVersion)) return;
+  if (cache.notifiedTag === cache.latestTag && cache.notifiedAt && now - cache.notifiedAt < WEEK_MS) return;
+
+  cache.notifiedTag = cache.latestTag;
+  cache.notifiedAt = now;
+  all[repository] = cache;
+  writeCache(cachePath, all);
+  const command = `npx skills@1.5.23 add '${repository}#${cache.latestTag}' --global --agent universal claude-code --skill ${name} --yes`;
+  process.stdout.write(
+    `UPDATE_AVAILABLE: A newer 1AboveIO skills release (${cache.latestTag}) is available; this skill is `
+      + `v${localVersion.join('.')}. Ask once whether to refresh ${name}. On approval run \`${command}\`. `
+      + 'The refreshed instructions apply next session. Either way, continue the current task and do not ask again this session.\n',
+  );
+}
+
+try { main(); } catch { /* Update checks are advisory and always fail silent. */ }