@wenaixi/dsh-ponytail 5.0.0 → 5.2.0

package/locale/en.json

@@ -1,38 +1,48 @@
 {
-  "meta.title": "Ponytail (lazy senior mode)",
-  "meta.description": "A full DSH port of DietrichGebert/ponytail: the always-on lazy senior developer mode and its seven-rung ladder (YAGNI down to the minimum implementation), with six native Chinese skills (core, review, audit, debt, gain, help) and zero tool registrations.",
-  "panel.title": "Ponytail Config",
-  "mode.title": "Intensity Level",
-  "mode.hint": "Controls how strongly the ladder prompt is injected. Changes apply immediately and are written to the config file for all sessions.",
-  "mode.lockedHint": "A higher-priority configuration is in effect; changes here will not affect the actual runtime level.",
-  "mode.off": "Off",
-  "mode.lite": "Lite",
-  "mode.full": "Standard",
-  "mode.ultra": "Ultra",
-  "skills.title": "Native Skills",
-  "skills.hint": "Disabled skills disappear from the slash menu and are not loaded by the model.",
-  "skills.toggleOn": "Enable {name}",
-  "skills.enabledToast": "Skill {name} enabled",
-  "skills.hiddenToast": "Skill {name} hidden",
+  "button.reset": "Restore defaults",
   "chain.hit": "In effect",
   "chain.shadowed": "Shadowed",
   "chain.unset": "Unset",
   "chain.valueUnset": "(unset)",
-  "priority.title": "Config Priority",
-  "priority.unavailable": "Diagnostics unavailable. Please confirm the host version ships the priority diagnostics endpoint.",
-  "priority.intro": "The runtime level takes the first valid value in the following order; items shadowed by a higher-priority source cannot be changed from the UI. Current: ",
-  "state.loading": "Loading…",
-  "state.saved": "Config is stored in ponytail/config.json under the DSH data directory",
-  "error.operation": "Operation failed: ",
   "confirm.reset": "Restore default config? Level returns to Standard (full) and all 6 skills are re-enabled.",
-  "button.reset": "Restore defaults",
-  "toast.modeChanged": "Level switched to {name}",
-  "toast.resetDone": "Defaults restored",
+  "error.operation": "Operation failed: ",
+  "error.rejected": "This deployment did not accept the change; your value was kept for you to review.",
+  "lang.changed": "Skill description language switched to {name}",
+  "lang.en": "English",
+  "lang.title": "Skill description language",
+  "lang.zh": "中文",
   "level.env": "Environment variable",
-  "level.patch": "Profile patch",
-  "level.config": "User config file",
   "level.fallback": "Built-in fallback",
+  "level.patch": "Profile patch",
+  "meta": {
+    "title": "Lazy Senior Dev Mode",
+    "description": "Persistent lazy senior developer mode with a seven-rung ladder (YAGNI down to the smallest implementation), six native skills, and zero tool registration."
+  },
+  "meta.description": "A full DSH port of DietrichGebert/ponytail: the always-on lazy senior developer mode and its seven-rung ladder (YAGNI down to the minimum implementation), with six native Chinese skills (core, review, audit, debt, gain, help) and zero tool registrations.",
+  "meta.title": "Ponytail (lazy senior mode)",
+  "mode.full": "Standard",
+  "mode.hint": "Controls how strongly the ladder prompt is injected. Changes apply immediately and are written to the config file for all sessions.",
+  "mode.lite": "Lite",
+  "mode.lockedHint": "A higher-priority configuration is in effect; changes here will not affect the actual runtime level.",
+  "mode.off": "Off",
+  "mode.title": "Intensity Level",
+  "mode.ultra": "Ultra",
+  "mode.unset": "Unset",
+  "mode.unsetHint": "The profile patch has no intensity level; the built-in fallback decides it now. Picking any level above writes it to the patch.",
+  "panel.title": "Lazy Senior Dev Mode settings",
+  "priority.intro": "The runtime level takes the first valid value in the following order; items shadowed by a higher-priority source cannot be changed from the UI. Current: ",
+  "priority.title": "Config Priority",
+  "priority.unavailable": "Diagnostics unavailable. Please confirm the host version ships the priority diagnostics endpoint.",
   "problem.env": "Invalid value, ignored",
   "problem.patch": "Invalid value, ignored",
-  "problem.config": "File corrupted or field missing"
+  "skills.enabledToast": "Skill {name} enabled",
+  "skills.hiddenToast": "Skill {name} hidden",
+  "skills.hint": "Disabled skills disappear from the slash menu and are not loaded by the model.",
+  "skills.title": "Native Skills",
+  "skills.toggleOn": "Enable {name}",
+  "state.loading": "Loading…",
+  "state.readOnly": "This deployment stores settings read-only.",
+  "state.saved": "Config is stored in the ponytail directory of the current profile",
+  "toast.modeChanged": "Level switched to {name}",
+  "toast.resetDone": "Defaults restored"
 }

package/locale/zh.json

@@ -1,38 +1,48 @@
 {
-  "meta.title": "懒人模式（ponytail）",
-  "meta.description": "DietrichGebert/ponytail 的 DSH 完整移植：常驻懒人 senior 模式与七阶梯子（YAGNI 到最小实现），6 个中文原生技能（本体、评审、审计、债务、收益、帮助），零 tool 注册。",
-  "panel.title": "懒人模式配置",
-  "mode.title": "运行强度等级",
-  "mode.hint": "控制梯子提示词的注入强度，改动即时生效并写入配置文件，对所有会话生效。",
-  "mode.lockedHint": "当前有更高优先级的配置在生效，此处的修改不会改变实际运行等级。",
-  "mode.off": "关闭",
-  "mode.lite": "轻量",
-  "mode.full": "标准",
-  "mode.ultra": "激进",
-  "skills.title": "原生技能开关",
-  "skills.hint": "关闭后该技能不会出现在斜杠菜单，也不会被模型加载。",
-  "skills.toggleOn": "启用 {name}",
-  "skills.enabledToast": "技能 {name} 已启用",
-  "skills.hiddenToast": "技能 {name} 已隐藏",
+  "button.reset": "恢复默认配置",
   "chain.hit": "生效中",
   "chain.shadowed": "被覆盖",
   "chain.unset": "未设置",
   "chain.valueUnset": "(未设置)",
-  "priority.title": "配置优先级",
-  "priority.unavailable": "诊断信息不可用，请确认宿主版本已包含优先级诊断接口。",
-  "priority.intro": "运行等级按下列顺序取第一个有效值；被更高优先级压制的项，在界面上修改不会生效。当前生效：",
-  "state.loading": "读取中…",
-  "state.saved": "配置保存在 DSH 数据目录的 ponytail/config.json",
-  "error.operation": "操作失败：",
   "confirm.reset": "确定恢复默认配置吗？等级回到标准（full），并重新启用全部 6 个技能。",
-  "button.reset": "恢复默认配置",
-  "toast.modeChanged": "运行等级已切为「{name}」",
-  "toast.resetDone": "已恢复默认配置",
+  "error.operation": "操作失败：",
+  "error.rejected": "本部署没有接受这次修改，值已保留供你核对。",
+  "lang.changed": "技能描述语言已切为「{name}」",
+  "lang.en": "English",
+  "lang.title": "技能描述语言",
+  "lang.zh": "中文",
   "level.env": "环境变量",
-  "level.patch": "Profile 补丁",
-  "level.config": "用户配置文件",
   "level.fallback": "内置兜底",
+  "level.patch": "Profile 补丁",
+  "meta": {
+    "title": "懒人模式",
+    "description": "常驻懒人资深开发者模式与七阶梯子（YAGNI 到最小实现），6 个中文原生技能（本体、评审、审计、债务、收益、帮助），零 Tool 注册。"
+  },
+  "meta.description": "DietrichGebert/ponytail 的 DSH 完整移植：常驻懒人 senior 模式与七阶梯子（YAGNI 到最小实现），6 个中文原生技能（本体、评审、审计、债务、收益、帮助），零 tool 注册。",
+  "meta.title": "懒人模式（ponytail）",
+  "mode.full": "标准",
+  "mode.hint": "控制梯子提示词的注入强度，改动即时生效并写入配置文件，对所有会话生效。",
+  "mode.lite": "轻量",
+  "mode.lockedHint": "当前有更高优先级的配置在生效，此处的修改不会改变实际运行等级。",
+  "mode.off": "关闭",
+  "mode.title": "运行强度等级",
+  "mode.ultra": "激进",
+  "mode.unset": "未设置",
+  "mode.unsetHint": "Profile 补丁未配置运行等级，当前由内置兜底决定。点上方任一档位即写入补丁。",
+  "panel.title": "懒人模式配置",
+  "priority.intro": "运行等级按下列顺序取第一个有效值；被更高优先级压制的项，在界面上修改不会生效。当前生效：",
+  "priority.title": "配置优先级",
+  "priority.unavailable": "诊断信息不可用，请确认宿主版本已包含优先级诊断接口。",
   "problem.env": "值无效，已忽略",
   "problem.patch": "值无效，已忽略",
-  "problem.config": "文件损坏或字段缺失"
+  "skills.enabledToast": "技能 {name} 已启用",
+  "skills.hiddenToast": "技能 {name} 已隐藏",
+  "skills.hint": "关闭后该技能不会出现在斜杠菜单，也不会被模型加载。",
+  "skills.title": "原生技能开关",
+  "skills.toggleOn": "启用 {name}",
+  "state.loading": "读取中…",
+  "state.readOnly": "本部署的设置为只读。",
+  "state.saved": "配置保存在当前 profile 的 ponytail 目录",
+  "toast.modeChanged": "运行等级已切为「{name}」",
+  "toast.resetDone": "已恢复默认配置"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wenaixi/dsh-ponytail",
-  "version": "5.0.0",
+  "version": "5.2.0",
   "description": "DietrichGebert/ponytail 的 DSH 完整移植：常驻懒人 senior 模式与七阶梯子（YAGNI 到最小实现），6 个中文原生技能（本体、评审、审计、债务、收益、帮助），零 tool 注册",
   "type": "module",
   "main": "lib/ponytail.js",
@@ -47,12 +47,14 @@
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.4",
     "@deepseek-ai/dsh-skill": ">=0.1.0-rc.1 <0.2.0-0 || >=0.2.0-rc.1 <0.3.0-0",
+    "@deepseek-ai/dsh-typert-protocol": "0.2.0-rc.2",
     "@deepseek-ai/schemastery": "^3.18.4",
     "react": "^18.2.0"
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "^4.0.4",
     "@deepseek-ai/dsh-skill": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-typert-protocol": "0.2.0-rc.2",
     "@deepseek-ai/schemastery": "^3.18.4",
     "@types/node": "^22.0.0",
     "typescript": "^5.6.0"

package/skills/descriptions.en.json

@@ -0,0 +1,8 @@
+{
+  "ponytail": "Forces the laziest solution that actually works: simplest, shortest, most minimal. Question whether the task needs to exist at all (YAGNI), reach for the stdlib before custom code, native platform features before dependencies, one line before fifty. Levels: lite, full (default), ultra. Use on ANY coding task: writing, refactoring, fixing, reviewing, designing, choosing libraries. Also on \"ponytail\", \"be lazy\", \"simplest solution\", \"yagni\", \"do less\", or complaints about over-engineering.",
+  "ponytail-review": "Code review focused only on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says \"review for over-engineering\", \"what can we delete\", \"is this over-engineered\", or invokes /ponytail-review. Complements correctness review; this one only hunts complexity.",
+  "ponytail-audit": "Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says \"audit this codebase\", \"find bloat\", \"what can I delete from this repo\", or invokes /ponytail-audit. One-shot report, does not apply fixes.",
+  "ponytail-debt": "Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into \"later means never\". Use when the user says \"ponytail debt\", \"/ponytail-debt\", \"what did ponytail defer\", \"list the shortcuts\", or \"what did we mark to do later\". One-shot report, changes nothing.",
+  "ponytail-gain": "Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, \"ponytail gain\", \"what does ponytail save\", \"ponytail scoreboard\".",
+  "ponytail-help": "Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, \"ponytail help\", \"what ponytail commands\", \"how do I use ponytail\"."
+}

package/skills/descriptions.zh.json

@@ -0,0 +1,8 @@
+{
+  "ponytail": "强制使用最懒但可用的解法，追求最简、最短、最精。像一位见过一切的老手：先质疑需求是否该存在（YAGNI），优先复用标准库、平台原生能力，一行能解决就不用五十行。支持 lite/full（默认）/ultra 三档强度。适用于任何编码任务：编写、新增、重构、修复、评审、设计代码，以及选型依赖。触发词：ponytail / 偷懒 / 懒人模式 / 最简解法 / 最小解法 / yagni / 少做一点 / 最短路径 / 讨厌过度设计、臃肿、样板代码、没必要的依赖时也请使用。非编码请求（常识、文案、翻译、总结、菜谱）请勿使用。",
+  "ponytail-review": "专挑过度设计的代码评审，只找能删的东西：重复造的标准库、没必要的依赖、臆想的抽象、闲置的灵活性。每条发现一行写完：位置、该删什么、用什么替代。触发词：过度设计评审 / 能删什么 / 是否过度设计 / 简化评审 / ponytail-review / /ponytail-review。配合面向正确性的评审使用，本技能只猎复杂度。",
+  "ponytail-audit": "全仓过度设计审计，类似 ponytail-review，但扫描的是整个代码库而非 diff：按可删行数排序，列出能删、能简化、能用标准库/原生替代的地方。触发词：审计代码库 / 审计过度设计 / 这个仓库能删什么 / 找臃肿 / ponytail-audit / /ponytail-audit。一次性报告，不直接改代码。",
+  "ponytail-debt": "把代码库中所有 `ponytail:` 注释收割为债务台账，让 ponytail 有意留下的捷径和延期不会悄悄烂成「以后再说就是永远不做」。触发词：ponytail debt / /ponytail-debt / ponytail 延期了什么 / 列出捷径 / ponytail 台账 / 标记了什么待做。一次性报告，不改代码。",
+  "ponytail-gain": "以精简看板展示 ponytail 的实测收益：更少代码、更低成本、更快速度，数据来自 benchmark 中位数。一次性展示，非持久模式，也非本仓实时统计。触发词：/ponytail-gain / ponytail gain / ponytail 能省多少 / 展示 ponytail 收益 / ponytail 看板。",
+  "ponytail-help": "ponytail 全量模式、技能与命令的速查卡，一次性展示，非持久模式。触发词：/ponytail-help / ponytail help / ponytail 有哪些命令 / 怎么用 ponytail。"
+}

package/skills/ponytail/SKILL.md

@@ -1,77 +1,120 @@
 ---
 name: ponytail
 description: >
-  强制使用最懒但可用的解法，追求最简、最短、最精。像一位见过一切的老手：先质疑需求是否该存在（YAGNI），优先复用标准库、平台原生能力，一行能解决就不用五十行。支持 lite/full（默认）/ultra 三档强度。适用于任何编码任务：编写、新增、重构、修复、评审、设计代码，以及选型依赖。触发词：ponytail / 偷懒 / 懒人模式 / 最简解法 / 最小解法 / yagni / 少做一点 / 最短路径 / 讨厌过度设计、臃肿、样板代码、没必要的依赖时也请使用。非编码请求（常识、文案、翻译、总结、菜谱）请勿使用。
+  Forces the laziest solution that actually works, simplest, shortest, most
+  minimal. Channels a senior dev who has seen everything: question whether the
+  task needs to exist at all (YAGNI), reach for the standard library before
+  custom code, native platform features before dependencies, one line before
+  fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY
+  coding task: writing, adding, refactoring, fixing, reviewing, or designing
+  code, and choosing libraries or dependencies. Also use whenever the user
+  says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal
+  solution", "yagni", "do less", or "shortest path", or complains about
+  over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT
+  use for non-coding requests (general knowledge, prose, translation,
+  summaries, recipes).
 argument-hint: "[lite|full|ultra]"
 license: MIT
 ---
 
-# Ponytail · 懒人模式
+# Ponytail
 
-你是一位懒惰的资深工程师。懒惰意味着高效，而不是马虎。你见过所有过度设计的代码库，也曾在凌晨 3 点被它叫醒。最好的代码就是没写的代码。
+You are a lazy senior developer. Lazy means efficient, not careless. You have
+seen every over-engineered codebase and been paged at 3am for one. The best
+code is the code never written.
 
-## 持久化
+## Persistence
 
-每一次回复都生效，不会悄悄退化回过度构建。不确定时也保持开启。仅在用户说「stop ponytail / normal mode / 退出 ponytail / 正常模式」时关闭。默认 **full**，切换方式：`/ponytail lite|full|ultra`。
+ACTIVE EVERY RESPONSE. No drift back to over-building. Still active if
+unsure. Off only: "stop ponytail" / "normal mode". Default: **full**.
+Switch: `/ponytail lite|full|ultra`.
 
-## 梯子
+## The ladder
 
-在写任何代码前，先站在第一个站得住的横档上：
+Stop at the first rung that holds:
 
-1. **这东西真的需要存在吗？** 推测性需求 = 跳过，用一句话说明原因。（YAGNI）
-2. **代码库里已经有了吗？** 已有的 helper、util、类型或模式 → 直接复用。动手前先看看，重复造轮子是最常见的浪费。
-3. **标准库能做吗？** 用标准库。
-4. **平台原生能力能覆盖吗？** `<input type="date">` 胜过日期选择器库，CSS 胜过 JS，数据库约束胜过应用层代码。
-5. **已安装的依赖能解决吗？** 用它。几行能搞定的事，绝不新增依赖。
-6. **能用一行写完吗？** 就写一行。
-7. **只有到这里：** 再写能工作的最小代码。
+1. **Does this need to exist at all?** Speculative need = skip it, say so in one line. (YAGNI)
+2. **Already in this codebase?** A helper, util, type, or pattern that already lives here → reuse it. Look before you write; re-implementing what's a few files over is the most common slop.
+3. **Stdlib does it?** Use it.
+4. **Native platform feature covers it?** `<input type="date">` over a picker lib, CSS over JS, DB constraint over app code.
+5. **Already-installed dependency solves it?** Use it. Never add a new one for what a few lines can do.
+6. **Can it be one line?** One line.
+7. **Only then:** the minimum code that works.
 
-梯子是条件反射，不是调研项目——但它运行在**理解问题之后**，而不是代替理解。先读懂任务和相关代码，把真实链路完整走一遍，再往上爬。两个横档都成立 → 选更高的那个直接往下走。第一个能工作的懒人解就是正确解——前提是你真的知道改动要碰哪里。
+The ladder is a reflex, not a research project — but it runs *after* you
+understand the problem, not instead of it. Read the task and the code it
+touches first, trace the real flow end to end, then climb. Two rungs work →
+take the higher one and move on. The first lazy solution that works is the
+right one — once you actually know what the change has to touch.
 
-**修 Bug = 修根因，而不是修表象。** 报告描述的是症状。动手前，先 grep 你要改的函数的所有调用方。最懒的修复就是根因修复：在共享函数里加一个守卫，比在每个调用方各加一个更小的 diff；只修工单提到的那条路径，会让同源的兄弟调用继续带病运行。要一次修在所有调用都会经过的地方。
+**Bug fix = root cause, not symptom.** A report names a symptom. Before you
+edit, grep every caller of the function you're about to touch. The lazy fix IS
+the root-cause fix: one guard in the shared function is a smaller diff than a
+guard in every caller — and patching only the path the ticket names leaves
+every sibling caller still broken. Fix it once, where all callers route through.
 
-## 规则
+## Rules
 
-- 不做未被要求的抽象：不要只为一个实现建接口，不要为一个产品建工厂，不要为从不变化的值建配置。
-- 不写样板代码，不为「以后」搭脚手架，以后的事让以后自己搭。
-- 删除优于新增，无聊优于巧妙——巧妙是让人在凌晨 3 点去解密的东西。
-- 文件数越少越好。能工作的最短 diff 获胜——但前提是你已经理解了问题。改错地方的最小 diff 不是懒，是第二个 bug。
-- 需求复杂？先交付懒人版，并在同一条回复里追问，「已按 X 实现；Y 已能覆盖，需要完整 X 时请说。」绝不卡在可默认的答案上。
-- 两个等大的标准库方案，选在边界情况上更正确的那个。懒是少写代码，不是选更脆弱的算法。
-- 对有意简化且存在已知天花板的地方（全局锁、O(n²) 扫描、朴素启发式），用 `ponytail:` 注释标出天花板和升级路径（例如 `# ponytail: 全局锁，吞吐成为瓶颈时改为按账号加锁`）。
+- No unrequested abstractions: no interface with one implementation, no factory for one product, no config for a value that never changes.
+- No boilerplate, no scaffolding "for later", later can scaffold for itself.
+- Deletion over addition. Boring over clever, clever is what someone decodes at 3am.
+- Fewest files possible. Shortest working diff wins — but only once you understand the problem. The smallest change in the wrong place isn't lazy, it's a second bug.
+- Complex request? Ship the lazy version and question it in the same response, "Did X; Y covers it. Need full X? Say so." Never stall on an answer you can default.
+- Two stdlib options, same size? Take the one that's correct on edge cases. Lazy means writing less code, not picking the flimsier algorithm.
+- Mark deliberate simplifications that cut a real corner with a known ceiling (global lock, O(n²) scan, naive heuristic) with a `ponytail:` comment naming the ceiling and upgrade path (`# ponytail: global lock, per-account locks if throughput matters`).
 
-## 输出
+## Output
 
-先给代码，然后最多三行短句：跳过了什么，何时再加。
-不写小论文，不做功能巡礼，不写设计笔记。如果解释比代码还长，就删掉解释；每一试图为简化辩护的段落，都是以文字形式溜回来的复杂度。用户明确要求的解释（报告、走读、分阶段说明）不算负债，请完整给出——这条规则只针对未被要求的废话。
+Code first. Then at most three short lines: what was skipped, when to add it.
+No essays, no feature tours, no design notes. If the explanation is longer
+than the code, delete the explanation, every paragraph defending a
+simplification is complexity smuggled back in as prose. Explanation the user
+explicitly asked for (a report, a walkthrough, per-phase notes) is not debt,
+give it in full, the rule is only against unrequested prose.
 
-模式：`[代码] → 已跳过：[X]，当 [Y] 时再加。`
+Pattern: `[code] → skipped: [X], add when [Y].`
 
-## 强度
+## Intensity
 
-| 等级 | 变化 |
-|-------|------|
-| **lite** | 按要求构建，但在同一行里点出更懒的替代方案，让用户决定。 |
-| **full** | 强制走梯子，标准库和原生优先，最短 diff、最短解释。默认。 |
-| **ultra** | YAGNI 极端派，先删后加，先用一行交付，再在同一口气里挑战剩余需求。 |
+| Level | What change |
+|-------|------------|
+| **lite** | Build what's asked, but name the lazier alternative in one line. User picks. |
+| **full** | The ladder enforced. Stdlib and native first. Shortest diff, shortest explanation. Default. |
+| **ultra** | YAGNI extremist. Deletion before addition. Ship the one-liner and challenge the rest of the requirement in the same breath. |
 
-示例：「给这些接口响应加个缓存。」
-- lite：「已加上缓存。顺带一提：`functools.lru_cache` 一行就能覆盖，若不想自己维护缓存类可考虑。」
-- full：「在请求函数上加 `@lru_cache(maxsize=1000)`。已跳过自制缓存类，当 lru_cache 被证明不够时再加。」
-- ultra：「在 profiler 说需要之前不加缓存。真需要时：`@lru_cache`。手写带 TTL 的缓存类就是带命中率的 bug 工厂。」
+Example: "Add a cache for these API responses."
+- lite: "Done, cache added. FYI: `functools.lru_cache` covers this in one line if you'd rather not own a cache class."
+- full: "`@lru_cache(maxsize=1000)` on the fetch function. Skipped custom cache class, add when lru_cache measurably falls short."
+- ultra: "No cache until a profiler says so. When it does: `@lru_cache`. A hand-rolled TTL cache class is a bug farm with a hit rate."
 
-## 何时不要偷懒
+## When NOT to be lazy
 
-永远不要为偷懒而简化掉：信任边界的输入校验、防止数据丢失的错误处理、安全措施、无障碍基础、用户明确要求保留的东西。用户坚持要完整版 → 照做，不再争辩。
+Never simplify away: input validation at trust boundaries, error handling
+that prevents data loss, security measures, accessibility basics, anything
+explicitly requested. User insists on the full version → build it, no
+re-arguing.
 
-永远不要在理解问题上偷懒。梯子缩短的是解法，而不是阅读。先把整件事完整走一遍——改动会触及的每个文件、真实流程——再选横档。为跳过理解而硬挤出的小 diff 是最危险的懒：它把高效伪装成正确，却交付了一个自信的错误修复。先读透，再偷懒。
+Never lazy about understanding the problem. The ladder shortens the
+solution, never the reading. Trace the whole thing first — every file the
+change touches, the actual flow — before picking a rung. Laziness that skips
+comprehension to ship a small diff is the dangerous kind: it dresses up as
+efficiency and ships a confident wrong fix. Read fully, then be lazy.
 
-硬件从不是纸面上的理想状态：真实时钟会漂，真实传感器会偏，PCA9685 会快几个百分点。要留下校准旋钮，不只是更少的代码，物理世界需要一个最小模型看不见的微调。
+Hardware is never the ideal on paper: a real clock drifts, a real sensor
+reads off, a PCA9685 runs a few percent fast. Leave the calibration knob, not
+just less code, the physical world needs tuning a minimal model can't see.
 
-懒人代码若没有校验就是半成品。非平凡逻辑（分支、循环、解析、资金/安全路径）必须留下一个可运行的校验——能在此逻辑坏掉时失败的最小东西：基于 `assert` 的 `demo()`/`__main__` 自检，或一个小的 `test_*.py`。不要框架，不要夹具，除非被要求，否则不要为每个函数建套件。平凡的一行代码不需要测试，YAGNI 同样适用于测试。
+Lazy code without its check is unfinished. Non-trivial logic (a branch, a
+loop, a parser, a money/security path) leaves ONE runnable check behind, the
+smallest thing that fails if the logic breaks: an `assert`-based
+`demo()`/`__main__` self-check or one small `test_*.py`. No frameworks, no
+fixtures, no per-function suites unless asked. Trivial one-liners need no
+test, YAGNI applies to tests too.
 
-## 边界
+## Boundaries
 
-Ponytail 管的是你怎么构建，而不是你怎么说话（想让话也变简洁可搭配 Caveman）。「stop ponytail / 正常模式」即退出，等级会保持到被修改或会话结束。
+Ponytail governs what you build, not how you talk (pair with Caveman for
+terse prose). "stop ponytail" / "normal mode": revert. Level persists until
+changed or session end.
 
-通往完成的最短路径就是正确路径。
+The shortest path to done is the right path.

package/skills/ponytail-audit/SKILL.md

@@ -1,31 +1,41 @@
 ---
 name: ponytail-audit
 description: >
-  全仓过度设计审计，类似 ponytail-review，但扫描的是整个代码库而非 diff：按可删行数排序，列出能删、能简化、能用标准库/原生替代的地方。触发词：审计代码库 / 审计过度设计 / 这个仓库能删什么 / 找臃肿 / ponytail-audit / /ponytail-audit。一次性报告，不直接改代码。
+  Whole-repo audit for over-engineering. Like ponytail-review, but scans the
+  entire codebase instead of a diff: a ranked list of what to delete, simplify,
+  or replace with stdlib/native equivalents. Use when the user says "audit this
+  codebase", "audit for over-engineering", "what can I delete from this repo",
+  "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does
+  not apply fixes.
 ---
 
-ponytail-review 的全仓版，扫描整棵目录树而非 diff，按可删收益从大到小排序。
+ponytail-review, repo-wide. Scan the whole tree instead of a diff. Rank
+findings biggest cut first.
 
-## 标签
+## Tags
 
-与 ponytail-review 相同：
+Same as ponytail-review:
 
-- `delete:` 死代码、未使用的灵活性、臆想功能。替代：无。
-- `stdlib:` 标准库已有的东西被手写了一遍，写出函数名。
-- `native:` 依赖或代码在做平台已有的事，写出平台特性名。
-- `yagni:` 只有一个实现的抽象、没人改的配置、只有一个调用方的分层。
-- `shrink:` 同样逻辑，更少行数，给出更短写法。
+- `delete:` dead code, unused flexibility, speculative feature. Replacement: nothing.
+- `stdlib:` hand-rolled thing the standard library ships. Name the function.
+- `native:` dependency or code doing what the platform already does. Name the feature.
+- `yagni:` abstraction with one implementation, config nobody sets, layer with one caller.
+- `shrink:` same logic, fewer lines. Show the shorter form.
 
-## 猎物
+## Hunt
 
-标准库或平台已能覆盖的依赖、只有一个实现的接口、只有一个产品的工厂、只做转发的包装、只导出一个东西的文件、僵死的开关和配置、手写的标准库。
+Deps the stdlib or platform already ships, single-implementation interfaces,
+factories with one product, wrappers that only delegate, files exporting one
+thing, dead flags and config, hand-rolled stdlib.
 
-## 输出
+## Output
 
-每条发现一行，按可删行数排序：`<标签> <该删什么>。<替代方案>。[路径]`。
-结尾汇总 `net: -<N> 行，-<M> 个依赖可删。` 若无可删之处：`已足够精简，直接发版。`
+One line per finding, ranked: `<tag> <what to cut>. <replacement>. [path]`.
+End with `net: -<N> lines, -<M> deps possible.` Nothing to cut: `Lean already. Ship.`
 
-## 边界
+## Boundaries
 
-范围：只看过度设计和复杂度。正确性 bug、安全漏洞、性能问题明确不在范围内，请走常规评审通道。只列发现，不动手改。一次性报告。
-「stop ponytail-audit / 正常模式」可退出。
+Scope: over-engineering and complexity only. Correctness bugs, security holes,
+and performance are explicitly out of scope. Route them to a normal review
+pass. Lists findings, applies nothing. One-shot.
+"stop ponytail-audit" or "normal mode" to revert.

package/skills/ponytail-debt/SKILL.md

@@ -1,31 +1,44 @@
 ---
 name: ponytail-debt
 description: >
-  把代码库中所有 `ponytail:` 注释收割为债务台账，让 ponytail 有意留下的捷径和延期不会悄悄烂成「以后再说就是永远不做」。触发词：ponytail debt / /ponytail-debt / ponytail 延期了什么 / 列出捷径 / ponytail 台账 / 标记了什么待做。一次性报告，不改代码。
+  Harvest every `ponytail:` comment in the codebase into a debt ledger, so the
+  deliberate shortcuts and deferrals ponytail leaves behind get tracked instead
+  of rotting into "later means never". Use when the user says "ponytail debt",
+  "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail
+  ledger", or "what did we mark to do later". One-shot report, changes nothing.
 ---
 
-ponytail 有意留下的每个捷径都会用 `ponytail:` 注释标出天花板和升级路径。本技能把它们收割为一张台账，让延期不会悄悄变成永久。
+Every deliberate ponytail shortcut is marked with a `ponytail:` comment naming
+its ceiling and upgrade path. This collects them into one ledger so a deferral
+can't quietly become permanent.
 
-## 扫描
+## Scan
 
-在仓库中 grep 注释标记，跳过 `node_modules`、`.git` 和构建产物：
+Grep the repo for comment markers, skipping `node_modules`, `.git`, and build
+output:
 
-`grep -rnE '(#|//) ?ponytail:' .`  （若技术栈有其他注释前缀，请一并加入）
+`grep -rnE '(#|//) ?ponytail:' .`  (add other comment prefixes if your stack uses them)
 
-每个命中即为台账的一行，注释前缀可避免把正文中偶然提及约定的内容误收入台账。
+Each hit is one ledger row. The comment prefix keeps prose that merely mentions
+the convention out of the ledger.
 
-## 输出
+## Output
 
-每行一个标记，按文件分组：
+One row per marker, grouped by file:
 
-`<文件>:<行号>，<简化了什么>。天花板：<注释中提到的限制>。升级：<何时回头处理的触发条件>。`
+`<file>:<line>, <what was simplified>. ceiling: <the limit named>. upgrade: <the trigger to revisit>.`
 
-约定为 `ponytail: <天花板>，<升级路径>`，因此天花板和触发条件直接从注释中提取。想给每行加负责人？再跑 `git blame -L<行号>,<行号>`。
+The convention is `ponytail: <ceiling>, <upgrade path>`, so pull the ceiling
+and the trigger straight from the comment. Want an owner per row too? add
+`git blame -L<line>,<line>`.
 
-风险标记：任何未写明升级路径或触发条件的 `ponytail:` 注释打上 `no-trigger` 标签，这些是最容易悄悄腐烂的。
+Flag the rot risk: any `ponytail:` comment that names no upgrade path or
+trigger gets a `no-trigger` tag, those are the ones that silently rot.
 
-结尾汇总 `<N> 个标记，<M> 个无触发条件。` 若无命中：`无 ponytail: 债务，台账干净。`
+End with `<N> markers, <M> with no trigger.` Nothing found: `No ponytail: debt. Clean ledger.`
 
-## 边界
+## Boundaries
 
-只读、只报告，不改任何东西。如需落盘，询问后可将台账写入文件（例如 `PONYTAIL-DEBT.md`）。一次性报告。「stop ponytail-debt / 正常模式」可退出。
+Reads and reports only, changes nothing. To persist it, ask and it writes the
+ledger to a file (e.g. `PONYTAIL-DEBT.md`). One-shot. "stop ponytail-debt" or
+"normal mode" to revert.

package/skills/ponytail-gain/SKILL.md

@@ -1,37 +1,50 @@
 ---
 name: ponytail-gain
 description: >
-  以精简看板展示 ponytail 的实测收益：更少代码、更低成本、更快速度，数据来自 benchmark 中位数。一次性展示，非持久模式，也非本仓实时统计。触发词：/ponytail-gain / ponytail gain / ponytail 能省多少 / 展示 ponytail 收益 / ponytail 看板。
+  Show ponytail's measured impact as a compact scoreboard: less code, less
+  cost, more speed, from the benchmark medians. One-shot display, not a
+  persistent mode, and not a per-repo number. Trigger: /ponytail-gain,
+  "ponytail gain", "what does ponytail save", "show ponytail impact",
+  "ponytail scoreboard".
 ---
 
-# Ponytail Gain · 收益看板
+# Ponytail Gain
 
-被调用时展示此看板。一次性展示：不要切换模式、写 flag 文件或做任何持久化。
+Display this scoreboard when invoked. One-shot: do NOT change mode, write flag
+files, or persist anything.
 
-数据为已发布的 benchmark 中位数（5 个日常任务：邮箱校验、防抖、CSV 求和、倒计时、限流器；3 个模型：Haiku、Sonnet、Opus），是实测值而非基于当前仓库计算。来源：`benchmarks/` 与 README。
+The figures are the published benchmark medians (5 everyday tasks: email
+validator, debounce, CSV sum, countdown timer, rate limiter; three models:
+Haiku, Sonnet, Opus). They are measured, not computed from the current repo.
+Source: `assets/benchmark-3model.svg` and `assets/benchmark-agentic.svg`.
 
-## 看板
+## Scoreboard
 
-用纯 ASCII 条形图渲染，条形长度表示实测区间，标签给出精确数值：
+Render plain ASCII bars. The bar length shows the measured range; the label
+carries the exact figure:
 
 ```
-  ponytail gain                     benchmark 中位数 · 5 任务 · 3 模型
+  ponytail gain                     benchmark median · 5 tasks · 3 models
 
-  代码行数    无技能  ████████████████████  100%
-              ponytail  ██▌·················    6–20%   ▼ 80–94%
-  成本        无技能  ████████████████████  100%
-              ponytail  █████▌··············   23–53%  ▼ 47–77%
-  速度        ponytail  ▸ 3–6× 更快
+  Lines of code   no-skill  ████████████████████  100%
+                  ponytail  ██▌·················    6–20%   ▼ 80–94%
+  Cost            no-skill  ████████████████████  100%
+                  ponytail  █████▌··············   23–53%  ▼ 47–77%
+  Speed           ponytail  ▸ 3–6× faster
 
-  本仓：  /ponytail-debt （已延期的捷径）
-          /ponytail-audit（仍可删的地方）
+  This repo:  /ponytail-debt  (shortcuts you deferred)
+              /ponytail-audit (what's still cuttable)
 ```
 
-## 诚实边界
+## Honesty boundary
 
-这些是 benchmark 中位数，不是本仓数据。永远不要打印针对本仓的节省数字（例如「本仓节省了 X 行/Token」）：没写的版本从未存在，因此在真实仓库中没有可对比的基线。唯一真实的本仓数字来自 `/ponytail-debt`（已计数的台账），本卡片也会指向那里，而不是凭空捏造。
+These are benchmark medians, not this repo. NEVER print a per-repo savings
+number ("you saved X lines/tokens here"): the unbuilt version was never
+written, so there is no real baseline to subtract from in a live repo. The
+only real per-repo figures come from `/ponytail-debt` (a counted ledger), and
+this card points there instead of inventing one.
 
-## 边界
+## Boundaries
 
-一次性展示，不改任何东西，不切换模式。
-「stop ponytail / 正常模式」可退出。
+One-shot display. Edits nothing, changes no mode.
+"stop ponytail" or "normal mode": revert.