self-evolve-framework 1.4.0 → 1.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "self-evolve-framework",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "description": "CodeBuddy 自我进化飞轮 — 仅适用于 CodeBuddy IDE。Post-Edit 验证闭环 + 规则自动推荐 + 离线进化分析",
   "type": "module",
   "bin": {

package/template/rules/ponytail.mdc

@@ -1,33 +1,108 @@
 ---
-description: Ponytail - 懒人高级开发者模式。写最少、最安全的代码。
+description: >
+  Ponytail — 懒人高级开发者模式。强制写最少、最安全的代码。
+  每次对话 always 激活，用户说"stop ponytail"退出。
 alwaysApply: true
 ---
 
-## Ponytail 核心规则
+# Ponytail
 
-在写任何代码之前，先停在能解决问题的**最低台阶**上，按优先级检查：
+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.
 
-1. **这东西真的需要建吗？**（YAGNI）不需要就跳过
-2. **标准库已经提供了吗？** 直接用它
-3. **平台/框架原生功能能覆盖吗？** 直接用它
-4. **已安装的依赖能解决吗？** 直接用它
-5. **能一行搞定吗？** 就写一行
-6. **以上都不行？** 才写最少工作的代码
+## Persistence
 
-## 执行规则
+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`.
 
-- 不要创建未经明确要求的抽象
-- 能不引入新依赖就别引入
-- 不要写没人要的样板代码
-- 删除优于添加，无聊优于花哨，文件数量越少越好
-- 质疑复杂需求："你真的需要 X，还是 Y 可以覆盖？"
-- 当两种方法长度相同时，选边界情况更正确的那一个
-- 有意的简化用 `ponytail:` 注释标注，写明已知上限和升级路径
+## The ladder
 
-## 不偷懒的地方（必须认真对待）
+Stop at the first rung that holds:
 
-- 输入校验
-- 错误处理
-- 安全性
-- 可访问性
-- 任何明确要求的事情
+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 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
+
+- 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 with a `ponytail:` comment (`// ponytail: this exists`), simple reads as intent, not ignorance. Shortcut with a known ceiling (global lock, O(n²) scan, naive heuristic)? The comment names the ceiling and the 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.
+
+Pattern: `[code] → skipped: [X], add when [Y].`
+
+## Intensity
+
+| 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. |
+
+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.
+
+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.
+
+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.
+
+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 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/template/skills/ponytail/SKILL.md

@@ -1,133 +0,0 @@
----
-name: ponytail
-description: >
-  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 whenever
-  the user says "ponytail", "be lazy", "lazy mode", "simplest solution",
-  "minimal solution", "yagni", "do less", or "shortest path", and whenever
-  they complain about over-engineering, bloat, boilerplate, or unnecessary
-  dependencies.
-argument-hint: "[lite|full|ultra]"
-license: MIT
----
-
-# Ponytail
-
-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
-
-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. **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 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
-
-- 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 with a `ponytail:` comment (`// ponytail: this exists`), simple reads as intent, not ignorance. Shortcut with a known ceiling (global lock, O(n²) scan, naive heuristic)? The comment names the ceiling and the 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.
-
-Pattern: `[code] → skipped: [X], add when [Y].`
-
-## Intensity
-
-| 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. |
-
-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.
-
-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.
-
-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.
-
-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 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.
-
-## 执行引擎
-
-此 skill 附带 [DietrichGebert/ponytail](https://github.com/DietrichGebert/ponytail) 的完整执行组件：
-
-| 组件 | 路径 | 用途 |
-|------|------|------|
-| MCP 服务器 | `scripts/mcp/` | 与 IDE 深度集成，提供上下文感知的懒人建议 |
-| Hooks | `scripts/hooks/` | 代码提交/保存时自动触发懒人审计 |
-| AGENTS.md | 项目根目录 | 安装后自动注入的 agent 指令 |
-
-首次安装后，如果需要激活 MCP 集成：
-
-```bash
-node .codebuddy/skills/ponytail/scripts/mcp/index.js
-```

package/template/skills/ponytail/scripts/hooks/claude-codex-hooks.json

@@ -1,44 +0,0 @@
-{
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "startup|resume|clear|compact",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/ponytail-activate.js\"; exit 0",
-            "commandWindows": "if (Get-Command node -ErrorAction SilentlyContinue) { node \"$env:CLAUDE_PLUGIN_ROOT\\hooks\\ponytail-activate.js\" }",
-            "timeout": 5,
-            "statusMessage": "Loading ponytail mode..."
-          }
-        ]
-      }
-    ],
-    "SubagentStart": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/ponytail-subagent.js\"; exit 0",
-            "commandWindows": "if (Get-Command node -ErrorAction SilentlyContinue) { node \"$env:CLAUDE_PLUGIN_ROOT\\hooks\\ponytail-subagent.js\" }",
-            "timeout": 5,
-            "statusMessage": "Loading ponytail mode..."
-          }
-        ]
-      }
-    ],
-    "UserPromptSubmit": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/ponytail-mode-tracker.js\"; exit 0",
-            "commandWindows": "if (Get-Command node -ErrorAction SilentlyContinue) { node \"$env:CLAUDE_PLUGIN_ROOT\\hooks\\ponytail-mode-tracker.js\" }",
-            "timeout": 5,
-            "statusMessage": "Tracking ponytail mode..."
-          }
-        ]
-      }
-    ]
-  }
-}

package/template/skills/ponytail/scripts/hooks/copilot-hooks.json

@@ -1,21 +0,0 @@
-{
-  "version": 1,
-  "hooks": {
-    "sessionStart": [
-      {
-        "type": "command",
-        "bash": "node \"${PLUGIN_ROOT}/hooks/ponytail-activate.js\"",
-        "powershell": "node \"${PLUGIN_ROOT}\\hooks\\ponytail-activate.js\"",
-        "timeoutSec": 5
-      }
-    ],
-    "userPromptSubmitted": [
-      {
-        "type": "command",
-        "bash": "node \"${PLUGIN_ROOT}/hooks/ponytail-mode-tracker.js\"",
-        "powershell": "node \"${PLUGIN_ROOT}\\hooks\\ponytail-mode-tracker.js\"",
-        "timeoutSec": 5
-      }
-    ]
-  }
-}

package/template/skills/ponytail/scripts/hooks/ponytail-activate.js

@@ -1,91 +0,0 @@
-#!/usr/bin/env node
-// ponytail — Claude Code SessionStart activation hook
-//
-// Runs on every session start:
-//   1. Writes flag file at $CLAUDE_CONFIG_DIR/.ponytail-active (defaults to ~/.claude; statusline reads this)
-//   2. Emits ponytail ruleset as hidden SessionStart context
-//   3. Detects missing statusline config and emits setup nudge
-
-const fs = require('fs');
-const path = require('path');
-const { getDefaultMode, getClaudeDir, isShellSafe } = require('./ponytail-config');
-const { getPonytailInstructions } = require('./ponytail-instructions');
-const {
-  clearMode,
-  isCodex,
-  isCopilot,
-  setMode,
-  writeHookOutput,
-} = require('./ponytail-runtime');
-
-const claudeDir = getClaudeDir();
-const settingsPath = path.join(claudeDir, 'settings.json');
-
-const mode = getDefaultMode();
-
-// "off" mode — skip activation entirely, don't write flag or emit rules
-if (mode === 'off') {
-  clearMode();
-  const hookOutput = (isCodex || isCopilot) ? '' : 'OK';
-  writeHookOutput('SessionStart', 'off', hookOutput);
-  process.exit(0);
-}
-
-// 1. Write flag file
-try {
-  setMode(mode);
-} catch (e) {
-  // Silent fail -- flag is best-effort, don't block the hook
-}
-
-// 2. Emit the ponytail ruleset, filtered to the active intensity level.
-let output = getPonytailInstructions(mode);
-
-// 3. Detect missing statusline config — nudge Claude to help set it up
-if (!isCodex && !isCopilot) try {
-  let hasStatusline = false;
-  if (fs.existsSync(settingsPath)) {
-    // Strip UTF-8 BOM some editors prepend on Windows (breaks JSON.parse)
-    const raw = fs.readFileSync(settingsPath, 'utf8').replace(/^\uFEFF/, '');
-    const settings = JSON.parse(raw);
-    if (settings.statusLine) {
-      hasStatusline = true;
-    }
-  }
-
-  if (!hasStatusline) {
-    const isWindows = process.platform === 'win32';
-    const scriptName = isWindows ? 'ponytail-statusline.ps1' : 'ponytail-statusline.sh';
-    const scriptPath = path.join(__dirname, scriptName);
-    if (isShellSafe(scriptPath)) {
-      const command = isWindows
-        ? `powershell -ExecutionPolicy Bypass -File "${scriptPath}"`
-        : `bash "${scriptPath}"`;
-      const statusLineSnippet =
-        '"statusLine": { "type": "command", "command": ' + JSON.stringify(command) + ' }';
-      output += "\n\n" +
-        "STATUSLINE SETUP NEEDED: The ponytail plugin includes a statusline badge showing active mode " +
-        "(e.g. [PONYTAIL], [PONYTAIL:ULTRA]). It is not configured yet. " +
-        "To enable, add this to ~/.claude/settings.json: " +
-        statusLineSnippet + " " +
-        "Proactively offer to set this up for the user on first interaction.";
-    } else {
-      // ponytail: install path has shell metacharacters — don't embed it in a
-      // command snippet; have the agent wire it up by hand instead.
-      output += "\n\n" +
-        "STATUSLINE SETUP NEEDED: The ponytail plugin includes a statusline badge showing active mode. " +
-        "Its install path contains characters unsafe to embed in a shell command, so configure it manually: " +
-        "add a statusLine command of type \"command\" that runs " + scriptName +
-        " from the plugin's hooks directory to ~/.claude/settings.json, quoting/escaping the path for your shell. " +
-        "Proactively offer to set this up for the user on first interaction.";
-    }
-  }
-} catch (e) {
-  // Silent fail — don't block session start over statusline detection
-}
-
-try {
-  writeHookOutput('SessionStart', mode, output);
-} catch (e) {
-  // Silent fail — stdout closed/EPIPE at hook exit must not surface as a hook failure
-}

package/template/skills/ponytail/scripts/hooks/ponytail-config.js

@@ -1,122 +0,0 @@
-#!/usr/bin/env node
-// ponytail — shared configuration resolver
-//
-// Resolution order for default mode:
-//   1. PONYTAIL_DEFAULT_MODE environment variable
-//   2. Config file defaultMode field:
-//      - $XDG_CONFIG_HOME/ponytail/config.json (any platform, if set)
-//      - ~/.config/ponytail/config.json (macOS / Linux fallback)
-//      - %APPDATA%\ponytail\config.json (Windows fallback)
-//   3. 'full'
-
-const fs = require('fs');
-const path = require('path');
-const os = require('os');
-
-const DEFAULT_MODE = 'full';
-const VALID_MODES = ['off', 'lite', 'full', 'ultra', 'review'];
-const RUNTIME_MODES = ['off', 'lite', 'full', 'ultra'];
-
-function normalizeMode(mode) {
-  if (typeof mode !== 'string') return null;
-  const normalized = mode.trim().toLowerCase();
-  return RUNTIME_MODES.includes(normalized) ? normalized : null;
-}
-
-function normalizeConfigMode(mode) {
-  if (typeof mode !== 'string') return null;
-  const normalized = mode.trim().toLowerCase();
-  return VALID_MODES.includes(normalized) ? normalized : null;
-}
-
-function normalizePersistedMode(mode) {
-  return normalizeMode(mode) || normalizeConfigMode(mode);
-}
-
-// "stop ponytail" / "normal mode" turn ponytail off, but only as a standalone
-// command. Matching the phrase anywhere in the message turned it off mid-task
-// for ordinary requests like "add a normal mode toggle" — so require the whole
-// message to be the command, ignoring case and trailing punctuation.
-function isDeactivationCommand(text) {
-  const t = String(text || '').trim().toLowerCase().replace(/[.!?\s]+$/, '');
-  return t === 'stop ponytail' || t === 'normal mode';
-}
-
-// ponytail: only embed the plugin install path in a statusline shell command when
-// it's made of ordinary path characters. An allowlist beats escaping every shell's
-// metacharacters; a hostile clone path (quotes, &, $, backtick, ;, etc.) falls back
-// to manual setup instead. Allows : \ / for normal Windows and POSIX paths. Full
-// per-shell escaper only if a real need appears.
-function isShellSafe(p) {
-  return typeof p === 'string' && /^[A-Za-z0-9 _.\-:/\\~]+$/.test(p);
-}
-
-function getConfigDir() {
-  if (process.env.XDG_CONFIG_HOME) {
-    return path.join(process.env.XDG_CONFIG_HOME, 'ponytail');
-  }
-  if (process.platform === 'win32') {
-    return path.join(
-      process.env.APPDATA || path.join(os.homedir(), 'AppData', 'Roaming'),
-      'ponytail'
-    );
-  }
-  return path.join(os.homedir(), '.config', 'ponytail');
-}
-
-function getConfigPath() {
-  return path.join(getConfigDir(), 'config.json');
-}
-
-function getClaudeDir() {
-  // ponytail: CLAUDE_CONFIG_DIR overrides ~/.claude, matching Claude Code.
-  return process.env.CLAUDE_CONFIG_DIR || path.join(os.homedir(), '.claude');
-}
-
-function getDefaultMode() {
-  // 1. Environment variable (highest priority)
-  const envMode = process.env.PONYTAIL_DEFAULT_MODE;
-  if (envMode && VALID_MODES.includes(envMode.toLowerCase())) {
-    return envMode.toLowerCase();
-  }
-
-  // 2. Config file
-  try {
-    const configPath = getConfigPath();
-    const config = JSON.parse(fs.readFileSync(configPath, 'utf8'));
-    if (config.defaultMode && VALID_MODES.includes(config.defaultMode.toLowerCase())) {
-      return config.defaultMode.toLowerCase();
-    }
-  } catch (e) {
-    // Config file doesn't exist or is invalid — fall through
-  }
-
-  // 3. Default
-  return DEFAULT_MODE;
-}
-
-function writeDefaultMode(mode) {
-  const normalized = normalizeConfigMode(mode);
-  if (!normalized) return null;
-
-  const configPath = getConfigPath();
-  fs.mkdirSync(path.dirname(configPath), { recursive: true });
-  fs.writeFileSync(configPath, JSON.stringify({ defaultMode: normalized }, null, 2), 'utf8');
-  return normalized;
-}
-
-module.exports = {
-  DEFAULT_MODE,
-  VALID_MODES,
-  RUNTIME_MODES,
-  getDefaultMode,
-  getConfigDir,
-  getConfigPath,
-  getClaudeDir,
-  isShellSafe,
-  normalizeMode,
-  normalizeConfigMode,
-  normalizePersistedMode,
-  isDeactivationCommand,
-  writeDefaultMode,
-};

package/template/skills/ponytail/scripts/hooks/ponytail-instructions.js

@@ -1,94 +0,0 @@
-#!/usr/bin/env node
-// Shared Ponytail instruction builder for Claude hooks and Pi extension.
-
-const fs = require('fs');
-const path = require('path');
-const { DEFAULT_MODE, normalizeMode, normalizePersistedMode } = require('./ponytail-config');
-
-const INDEPENDENT_MODES = new Set(['review']);
-const SKILL_PATH = path.join(__dirname, '..', 'skills', 'ponytail', 'SKILL.md');
-
-function filterSkillBodyForMode(body, mode) {
-  const effectiveMode = normalizeMode(mode) || DEFAULT_MODE;
-  const withoutFrontmatter = String(body || '').replace(/^---[\s\S]*?---\s*/, '');
-
-  // Only the intensity table rows and worked examples are mode-specific, and
-  // both are keyed by a mode name (lite/full/ultra). A bullet whose label is
-  // not a mode — e.g. "No unrequested abstractions: ..." — is a normal rule
-  // and must be kept verbatim.
-  return withoutFrontmatter
-    .split(/\r?\n/)
-    .filter((line) => {
-      const tableLabel = line.match(/^\|\s*\*\*(.+?)\*\*\s*\|/);
-      if (tableLabel) {
-        const labelMode = normalizeMode(tableLabel[1].trim());
-        if (labelMode) return labelMode === effectiveMode;
-      }
-
-      const exampleLabel = line.match(/^-\s*([^:]+):\s*/);
-      if (exampleLabel) {
-        const labelMode = normalizeMode(exampleLabel[1].trim());
-        if (labelMode) return labelMode === effectiveMode;
-      }
-
-      return true;
-    })
-    .join('\n');
-}
-
-function getFallbackInstructions(mode) {
-  return 'PONYTAIL MODE ACTIVE — level: ' + mode + '\n\n' +
-    'You are a lazy senior developer. Lazy means efficient, not careless. The best code is the code never written.\n\n' +
-    '## Persistence\n\n' +
-    'ACTIVE EVERY RESPONSE. No drift back to over-building. Still active if unsure. Off only: "stop ponytail" / "normal mode".\n\n' +
-    'Current level: **' + mode + '**. Switch: `/ponytail lite|full|ultra`.\n\n' +
-    '## The ladder\n\n' +
-    'Before any code, stop at the first rung that holds (the ladder runs after you understand the problem, not instead of it — read the code it touches and trace the real flow first):\n' +
-    '1. Does this need to be built at all? (YAGNI)\n' +
-    '2. Does it already exist in this codebase? Reuse what is already here, do not re-write it.\n' +
-    '3. Does the standard library do this? Use it.\n' +
-    '4. Does a native platform feature cover it? Use it.\n' +
-    '5. Does an already-installed dependency solve it? Use it.\n' +
-    '6. Can this be one line? Make it one line.\n' +
-    '7. Only then: write the minimum code that works.\n\n' +
-    'Bug fix = root cause, not symptom: grep every caller of the function you touch and fix the shared function once (a smaller diff than one guard per caller); patching only the path the ticket names leaves a sibling caller broken.\n\n' +
-    '## Rules\n\n' +
-    'No abstractions that were not requested. No avoidable dependencies. No boilerplate nobody asked for. ' +
-    'Deletion over addition. Boring over clever. Fewest files possible. ' +
-    'Ship the lazy version and question the complex request in the same response — never stall. ' +
-    'Between two same-size stdlib options, pick the one correct on edge cases. ' +
-    'Mark intentional simplifications with a `ponytail:` comment — a shortcut with a known ceiling names the ceiling and the upgrade path in the comment.\n\n' +
-    '## Output\n\n' +
-    'Code first. Then at most three short lines: what was skipped, when to add it. ' +
-    'If the explanation is longer than the code, delete the explanation. ' +
-    'Explanation the user explicitly asked for is not debt, give it in full.\n\n' +
-    '## When NOT to be lazy\n\n' +
-    'Never simplify away: understanding the problem (read it fully and trace the real flow before picking a rung — a small diff you do not understand is just laziness dressed up as efficiency), input validation at trust boundaries, error handling that prevents data loss, ' +
-    'security measures, accessibility basics, the calibration real hardware needs (the platform is never the spec ideal), anything the user explicitly asked to keep. ' +
-    'Lazy code without its check is unfinished: non-trivial logic leaves ONE runnable check behind (assert-based demo/self-check or one small test file; no frameworks). Trivial one-liners need no test.\n\n' +
-    '## Boundaries\n\n' +
-    'Ponytail governs what you build, not how you talk. "stop ponytail" or "normal mode": revert. Level persists until changed or session end.';
-}
-
-function getPonytailInstructions(mode) {
-  const configuredMode = normalizePersistedMode(mode) || DEFAULT_MODE;
-
-  if (INDEPENDENT_MODES.has(configuredMode)) {
-    return 'PONYTAIL MODE ACTIVE — level: ' + configuredMode + '. Behavior defined by /ponytail-' + configuredMode + ' skill.';
-  }
-
-  const effectiveMode = normalizeMode(configuredMode) || DEFAULT_MODE;
-
-  try {
-    return 'PONYTAIL MODE ACTIVE — level: ' + effectiveMode + '\n\n' +
-      filterSkillBodyForMode(fs.readFileSync(SKILL_PATH, 'utf8'), effectiveMode);
-  } catch (e) {
-    return getFallbackInstructions(effectiveMode);
-  }
-}
-
-module.exports = {
-  filterSkillBodyForMode,
-  getFallbackInstructions,
-  getPonytailInstructions,
-};

package/template/skills/ponytail/scripts/hooks/ponytail-mode-tracker.js

@@ -1,55 +0,0 @@
-#!/usr/bin/env node
-// ponytail — UserPromptSubmit hook to track which ponytail mode is active
-// Inspects user input for /ponytail commands and writes mode to flag file
-
-const { getDefaultMode, isDeactivationCommand } = require('./ponytail-config');
-const { clearMode, setMode, writeHookOutput } = require('./ponytail-runtime');
-
-let input = '';
-process.stdin.on('data', chunk => { input += chunk; });
-process.stdin.on('end', () => {
-  try {
-    // Strip UTF-8 BOM some shells prepend when piping (breaks JSON.parse)
-    const data = JSON.parse(input.replace(/^\uFEFF/, ''));
-    const prompt = (data.prompt || '').trim().toLowerCase();
-
-    // Match /ponytail commands
-    if (/^[/@$]ponytail/.test(prompt)) {
-      const parts = prompt.split(/\s+/);
-      const cmd = parts[0].replace(/^[@$]/, '/');
-      const arg = parts[1] || '';
-
-      let mode = null;
-
-      if (cmd === '/ponytail-review' || cmd === '/ponytail:ponytail-review') {
-        mode = 'review';
-      } else if (cmd === '/ponytail' || cmd === '/ponytail:ponytail') {
-        if (arg === 'lite') mode = 'lite';
-        else if (arg === 'full') mode = 'full';
-        else if (arg === 'ultra') mode = 'ultra';
-        else if (arg === 'off') mode = 'off';
-        else mode = getDefaultMode();
-      }
-
-      if (mode && mode !== 'off') {
-        setMode(mode);
-        writeHookOutput(
-          'UserPromptSubmit',
-          mode,
-          'PONYTAIL MODE CHANGED — level: ' + mode,
-        );
-      } else if (mode === 'off') {
-        clearMode();
-        writeHookOutput('UserPromptSubmit', 'off', 'PONYTAIL MODE OFF');
-      }
-    }
-
-    // Detect deactivation
-    if (isDeactivationCommand(prompt)) {
-      clearMode();
-      writeHookOutput('UserPromptSubmit', 'off', 'PONYTAIL MODE OFF');
-    }
-  } catch (e) {
-    // Silent fail
-  }
-});

package/template/skills/ponytail/scripts/hooks/ponytail-runtime.js

@@ -1,68 +0,0 @@
-const fs = require('fs');
-const path = require('path');
-const { getClaudeDir } = require('./ponytail-config');
-
-const STATE_FILE = '.ponytail-active';
-const isCopilot = Boolean(process.env.COPILOT_PLUGIN_DATA);
-const isCodex = !isCopilot && Boolean(process.env.PLUGIN_DATA);
-
-let stateDir = getClaudeDir();
-if (isCodex) stateDir = process.env.PLUGIN_DATA;
-if (isCopilot) stateDir = process.env.COPILOT_PLUGIN_DATA;
-
-const statePath = path.join(stateDir, STATE_FILE);
-
-function setMode(mode) {
-  fs.mkdirSync(path.dirname(statePath), { recursive: true });
-  fs.writeFileSync(statePath, mode);
-}
-
-function clearMode() {
-  try { fs.unlinkSync(statePath); } catch (e) {}
-}
-
-// Live mode written by activate/mode-tracker. Absent flag = ponytail off.
-function readMode() {
-  try {
-    return fs.readFileSync(statePath, 'utf8').trim() || null;
-  } catch (e) {
-    return null;
-  }
-}
-
-function writeHookOutput(event, mode, context = '') {
-  if (isCopilot) {
-    // Copilot reads additionalContext on SessionStart; ignores output elsewhere.
-    process.stdout.write(JSON.stringify(
-      event === 'SessionStart' && context ? { additionalContext: context } : {}));
-    return;
-  }
-  if (isCodex) {
-    const output = { systemMessage: `PONYTAIL:${mode.toUpperCase()}` };
-    if (context) {
-      output.hookSpecificOutput = {
-        hookEventName: event,
-        additionalContext: context,
-      };
-    }
-    process.stdout.write(JSON.stringify(output));
-    return;
-  }
-  // Native Claude: SessionStart accepts raw stdout, but SubagentStart needs the
-  // hookSpecificOutput JSON form or the context is dropped.
-  if (event === 'SubagentStart') {
-    process.stdout.write(JSON.stringify(
-      { hookSpecificOutput: { hookEventName: event, additionalContext: context } }));
-    return;
-  }
-  process.stdout.write(context);
-}
-
-module.exports = {
-  clearMode,
-  isCodex,
-  isCopilot,
-  readMode,
-  setMode,
-  writeHookOutput,
-};

package/template/skills/ponytail/scripts/hooks/ponytail-statusline.ps1

@@ -1,21 +0,0 @@
-# CLAUDE_CONFIG_DIR overrides ~/.claude, matching where the hooks write the flag (issue #34)
-$ClaudeDir = if ($env:CLAUDE_CONFIG_DIR) { $env:CLAUDE_CONFIG_DIR } else { Join-Path $HOME ".claude" }
-$Flag = Join-Path $ClaudeDir ".ponytail-active"
-if (-not (Test-Path $Flag)) {
-    exit 0
-}
-
-$Mode = ""
-try {
-    $Mode = (Get-Content $Flag -ErrorAction Stop | Select-Object -First 1).Trim()
-} catch {
-    exit 0
-}
-
-$Esc = [char]27
-if ([string]::IsNullOrEmpty($Mode) -or $Mode -eq "full") {
-    [Console]::Write("${Esc}[38;5;108m[PONYTAIL]${Esc}[0m")
-} else {
-    $Suffix = $Mode.ToUpperInvariant()
-    [Console]::Write("${Esc}[38;5;108m[PONYTAIL:$Suffix]${Esc}[0m")
-}

package/template/skills/ponytail/scripts/hooks/ponytail-statusline.sh

@@ -1,12 +0,0 @@
-#!/usr/bin/env bash
-# CLAUDE_CONFIG_DIR overrides ~/.claude, matching where the hooks write the flag (issue #34)
-flag="${CLAUDE_CONFIG_DIR:-$HOME/.claude}/.ponytail-active"
-[ -f "$flag" ] || exit 0
-
-mode=$(head -n1 "$flag" | tr -d '[:space:]')
-
-if [ -z "$mode" ] || [ "$mode" = "full" ]; then
-    printf '\033[38;5;108m[PONYTAIL]\033[0m'
-else
-    printf '\033[38;5;108m[PONYTAIL:%s]\033[0m' "$(printf '%s' "$mode" | tr '[:lower:]' '[:upper:]')"
-fi

package/template/skills/ponytail/scripts/hooks/ponytail-subagent.js

@@ -1,22 +0,0 @@
-#!/usr/bin/env node
-// ponytail — Claude Code SubagentStart hook
-//
-// SessionStart context is parent-thread only and never reaches subagents, so
-// without this every Task-spawned agent runs ponytail-unaware (issue #252).
-// When ponytail mode is active, inject the same ruleset into each subagent.
-
-const { getPonytailInstructions } = require('./ponytail-instructions');
-const { readMode, writeHookOutput } = require('./ponytail-runtime');
-
-const mode = readMode();
-
-// Absent flag or off → ponytail isn't active; inject nothing.
-if (!mode || mode === 'off') {
-  process.exit(0);
-}
-
-try {
-  writeHookOutput('SubagentStart', mode, getPonytailInstructions(mode));
-} catch (e) {
-  // Silent fail — a stdout error at hook exit must not surface as a hook failure.
-}

package/template/skills/ponytail/scripts/mcp/README.md

@@ -1,46 +0,0 @@
-# ponytail-mcp
-
-An MCP server that serves Ponytail's lazy-senior-dev instructions. It exposes
-the same ruleset the Claude hooks and Pi extension use, so every host emits
-identical rules.
-
-It is not a replacement for the always-on adapters. Ponytail normally lives in
-the system context every turn. MCP prompts are user-invoked, and there is no
-portable MCP primitive for "inject this into every turn" across hosts. So this
-server is the clean option for MCP hosts whose only injection point is the
-prompt menu, or that pull context through tools. See issue #70.
-
-## What it exposes
-
-- Prompt `ponytail`, returns the ruleset as a user message. Optional `mode`
-  argument: `lite`, `full`, or `ultra`. Omit it to use the configured default.
-- Tool `ponytail_instructions`, same text, plus `structuredContent`
-  (`{ mode, instructions }`), for hosts that pull context via tools or code
-  execution. Read-only.
-
-Mode resolution reuses `hooks/ponytail-config.js`, so `PONYTAIL_DEFAULT_MODE`
-and `~/.config/ponytail/config.json` work the same as everywhere else.
-
-## Run it
-
-```bash
-cd ponytail-mcp
-npm install
-node index.js        # speaks MCP over stdio
-```
-
-Point an MCP host at that command. Example client entry:
-
-```json
-{ "mcpServers": { "ponytail": { "command": "node", "args": ["ponytail-mcp/index.js"] } } }
-```
-
-## Test
-
-```bash
-npm test
-```
-
-Covers mode resolution and the instruction text. The MCP wiring in `index.js`
-is intentionally thin: it just maps the prompt and tool onto
-`buildInstructions`.

package/template/skills/ponytail/scripts/mcp/index.js

@@ -1,48 +0,0 @@
-#!/usr/bin/env node
-// Ponytail MCP server: serves the lazy-senior-dev ruleset over stdio as a
-// prompt (user-invoked) and a tool (for hosts that pull context via tools).
-// It does NOT replace the always-on adapters; it's the clean option for hosts
-// whose only injection point is the prompt menu (see #70).
-import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
-import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
-import { z } from "zod";
-
-import { MODES, buildInstructions, resolveMode } from "./instructions.js";
-
-const server = new McpServer({ name: "ponytail", version: "0.1.0" });
-
-const modeArg = z
-  .enum(MODES)
-  .optional()
-  .describe("Ponytail intensity: lite, full, or ultra. Omit for the configured default.");
-
-server.registerPrompt(
-  "ponytail",
-  {
-    title: "Ponytail mode",
-    description: "Lazy senior dev instructions: YAGNI, stdlib first, the smallest correct change.",
-    argsSchema: { mode: modeArg },
-  },
-  ({ mode }) => ({
-    messages: [{ role: "user", content: { type: "text", text: buildInstructions(mode) } }],
-  }),
-);
-
-server.registerTool(
-  "ponytail_instructions",
-  {
-    title: "Ponytail instructions",
-    description: "Return the Ponytail ruleset for the given intensity (lite, full, or ultra).",
-    inputSchema: { mode: modeArg },
-    outputSchema: { mode: z.string(), instructions: z.string() },
-    annotations: { readOnlyHint: true, openWorldHint: false },
-  },
-  ({ mode }) => {
-    const resolvedMode = resolveMode(mode);
-    const instructions = buildInstructions(resolvedMode);
-    const structuredContent = { mode: resolvedMode, instructions };
-    return { content: [{ type: "text", text: instructions }], structuredContent };
-  },
-);
-
-await server.connect(new StdioServerTransport());

package/template/skills/ponytail/scripts/mcp/instructions.js

@@ -1,26 +0,0 @@
-// Pure instruction selection for the Ponytail MCP server. No MCP/SDK imports,
-// so this stays unit-testable on its own. Reuses the same builder the Claude
-// hooks and Pi extension use, so every host emits identical rules.
-import { createRequire } from "node:module";
-
-const require = createRequire(import.meta.url);
-const { getPonytailInstructions } = require("../hooks/ponytail-instructions.js");
-const { getDefaultMode, normalizeMode } = require("../hooks/ponytail-config.js");
-
-// The three intensities the server offers. "off" has no instructions to serve.
-export const MODES = ["lite", "full", "ultra"];
-
-// Resolve a requested mode to a runtime intensity. Unknown, empty, or "off"
-// falls back to the configured default, then to "full".
-// ponytail: keep the surface to these three; "off"/"review" aren't served here.
-export function resolveMode(requested) {
-  const asked = normalizeMode(requested);
-  if (asked && asked !== "off") return asked;
-
-  const fallback = normalizeMode(getDefaultMode());
-  return fallback && fallback !== "off" ? fallback : "full";
-}
-
-export function buildInstructions(requested) {
-  return getPonytailInstructions(resolveMode(requested));
-}

package/template/skills/ponytail/scripts/mcp/package.json

@@ -1,13 +0,0 @@
-{
-  "name": "ponytail-mcp",
-  "version": "4.8.3",
-  "description": "MCP server that serves Ponytail's lazy-senior-dev instructions as a prompt and a tool.",
-  "private": true,
-  "type": "module",
-  "license": "MIT",
-  "scripts": { "test": "node --test ./test/*.test.js" },
-  "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.26.0",
-    "zod": "^3.23.0"
-  }
-}

package/template/skills/ponytail/scripts/mcp/test/instructions.test.js

@@ -1,22 +0,0 @@
-import assert from "node:assert/strict";
-import test from "node:test";
-
-import { MODES, resolveMode, buildInstructions } from "../instructions.js";
-
-test("resolveMode keeps valid intensities", () => {
-  for (const mode of MODES) assert.equal(resolveMode(mode), mode);
-});
-
-test("resolveMode falls back to a runtime intensity for off/unknown/empty", () => {
-  // PONYTAIL_DEFAULT_MODE could be anything in CI, so just assert the contract:
-  // never returns "off", "review", or junk — always one of the served modes.
-  for (const input of ["off", "review", "nonsense", "", undefined, null]) {
-    assert.ok(MODES.includes(resolveMode(input)), `resolveMode(${input}) must be a served mode`);
-  }
-});
-
-test("buildInstructions returns the ruleset tagged with the resolved mode", () => {
-  const text = buildInstructions("ultra");
-  assert.match(text, /PONYTAIL MODE ACTIVE/);
-  assert.match(text, /ultra/);
-});

package/template/skills/ponytail-audit/SKILL.md

@@ -1,41 +0,0 @@
----
-name: ponytail-audit
-description: >
-  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, repo-wide. Scan the whole tree instead of a diff. Rank
-findings biggest cut first.
-
-## Tags
-
-Same as ponytail-review:
-
-- `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
-
-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
-
-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/template/skills/ponytail-debt/SKILL.md

@@ -1,44 +0,0 @@
----
-name: ponytail-debt
-description: >
-  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.
----
-
-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 the repo for comment markers, skipping `node_modules`, `.git`, and build
-output:
-
-`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>.`
-
-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>`.
-
-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.
-
-End with `<N> markers, <M> with no trigger.` Nothing found: `No ponytail: debt. Clean ledger.`
-
-## Boundaries
-
-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/template/skills/ponytail-gain/SKILL.md

@@ -1,50 +0,0 @@
----
-name: ponytail-gain
-description: >
-  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
-
-Display this scoreboard when invoked. One-shot: do NOT change mode, write flag
-files, or persist anything.
-
-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: `benchmarks/` and the README.
-
-## Scoreboard
-
-Render plain ASCII bars. The bar length shows the measured range; the label
-carries the exact figure:
-
-```
-  ponytail gain                     benchmark median · 5 tasks · 3 models
-
-  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
-
-  This repo:  /ponytail-debt  (shortcuts you deferred)
-              /ponytail-audit (what's still cuttable)
-```
-
-## Honesty boundary
-
-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
-
-One-shot display. Edits nothing, changes no mode.
-"stop ponytail" or "normal mode": revert.

package/template/skills/ponytail-help/SKILL.md

@@ -1,69 +0,0 @@
----
-name: ponytail-help
-description: >
-  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".
----
-
-# Ponytail Help
-
-Display this reference card when invoked. One-shot, do NOT change mode,
-write flag files, or persist anything.
-
-## Levels
-
-| Level | Trigger | What change |
-|-------|---------|-------------|
-| **Lite** | `/ponytail lite` | Build what's asked, name the lazier alternative in one line. |
-| **Full** | `/ponytail` | The ladder enforced: YAGNI → stdlib → native → one line → minimum. Default. |
-| **Ultra** | `/ponytail ultra` | YAGNI extremist. Deletion before addition. Challenges requirements before building. |
-
-Level sticks until changed or session end.
-
-## Skills
-
-| Skill | Trigger | What it does |
-|-------|---------|--------------|
-| **ponytail** | `/ponytail` | Lazy mode itself. Simplest solution that works. |
-| **ponytail-review** | `/ponytail-review` | Over-engineering review: `L42: yagni: factory, one product. Inline.` |
-| **ponytail-gain** | `/ponytail-gain` | Measured-impact scoreboard: less code, less cost, more speed. |
-| **ponytail-help** | `/ponytail-help` | This card. |
-
-Codex uses `@ponytail`, `@ponytail-review`, and `@ponytail-help`; Claude Code
-and OpenCode use the slash-command forms above (OpenCode ships `/ponytail` and
-`/ponytail-review`).
-
-## Deactivate
-
-Say "stop ponytail" or "normal mode". Resume anytime with `/ponytail`.
-`/ponytail off` also works.
-
-## Configure Default Mode
-
-Default mode = `full`, auto-active every session. Change it:
-
-**Environment variable** (highest priority):
-```bash
-export PONYTAIL_DEFAULT_MODE=ultra
-```
-
-**Config file** (`~/.config/ponytail/config.json`, Windows: `%APPDATA%\ponytail\config.json`):
-```json
-{ "defaultMode": "lite" }
-```
-
-Set `"off"` to disable auto-activation on session start, activate manually
-with `/ponytail` when wanted.
-
-Resolution: env var > config file > `full`.
-
-## Update
-
-Enable auto-update once: open `/plugin`, go to Marketplaces, pick ponytail, Enable auto-update. Claude Code then pulls new versions at startup (run `/reload-plugins` when it prompts). Manual refresh: `/plugin marketplace update ponytail` then `/reload-plugins`.
-
-If `/plugin` is not recognized, your Claude Code is out of date. Update it (`npm install -g @anthropic-ai/claude-code@latest`, or `brew upgrade claude-code`) and restart. Other hosts use their own update flow.
-
-## More
-
-Full docs + examples: https://github.com/DietrichGebert/ponytail

package/template/skills/ponytail-review/SKILL.md

@@ -1,57 +0,0 @@
----
-name: ponytail-review
-description: >
-  Code review focused exclusively 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", "simplify review", or invokes
-  /ponytail-review. Complements correctness-focused review, this one only
-  hunts complexity.
----
-
-Review diffs for unnecessary complexity. One line per finding: location, what
-to cut, what replaces it. The diff's best outcome is getting shorter.
-
-## Format
-
-`L<line>: <tag> <what>. <replacement>.`, or `<file>:L<line>: ...` for
-multi-file diffs.
-
-Tags:
-
-- `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.
-
-## Examples
-
-❌ "This EmailValidator class might be more complex than necessary, have you
-considered whether all these validation rules are needed at this stage?"
-
-✅ `L12-38: stdlib: 27-line validator class. "@" in email, 1 line, real validation is the confirmation mail.`
-
-✅ `L4: native: moment.js imported for one format call. Intl.DateTimeFormat, 0 deps.`
-
-✅ `repo.py:L88: yagni: AbstractRepository with one implementation. Inline it until a second one exists.`
-
-✅ `L52-71: delete: retry wrapper around an idempotent local call. Nothing replaces it.`
-
-✅ `L30-44: shrink: manual loop builds dict. dict(zip(keys, values)), 1 line.`
-
-## Scoring
-
-End with the only metric that matters: `net: -<N> lines possible.`
-
-If there is nothing to cut, say `Lean already. Ship.` and stop.
-
-## Boundaries
-
-Scope: over-engineering and complexity only. Correctness bugs, security holes,
-and performance are explicitly out of scope. Route them to a normal review
-pass, not this one. A single smoke test or `assert`-based
-self-check is the ponytail minimum, not bloat, never flag it for deletion.
-Does not apply the fixes, only lists them.
-"stop ponytail-review" or "normal mode": revert to verbose review style.