@simpleapps-com/augur-skills 2026.4.10 → 2026.4.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@simpleapps-com/augur-skills",
-  "version": "2026.04.10",
+  "version": "2026.04.12",
   "description": "Install curated Claude Code skills",
   "license": "MIT",
   "type": "module",
@@ -25,7 +25,7 @@
     "vitest": "^2.0.0"
   },
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=24.0.0"
   },
   "scripts": {
     "build": "tsup",

package/skills/simpleapps/bash-simplicity/SKILL.md

@@ -94,6 +94,16 @@ Right: `Glob(pattern: "{path}/repo/src/components/**/*")`
 
 All project paths are known and predictable (see `simpleapps:wiki` Cross-Project Wiki Access). MUST NOT search the filesystem with `find` or download from the internet. Just use the dedicated tool with the known path.
 
+## Subagent Responsibility
+
+Subagents do NOT inherit this skill. They see only the prompt you give them. The primary agent MUST brief every subagent on bash-simplicity before delegating shell work, and owns the output that comes back.
+
+Every subagent prompt that touches Bash MUST include a one-liner: "One command per Bash call. No operators. Use dedicated tools (Read, Grep, Glob, Edit, Write) over shell equivalents."
+
+If a subagent returns a command containing any forbidden operator (see the table above), that is the primary agent's failure. Reject and ask for a re-plan, or translate into separate simple calls. Do not execute it. A subagent violating this is running on a stale prompt; fix the prompt.
+
+Parallel subagents each need their own briefing.
+
 ## Check Before Prompting
 
 Before running a command that will trigger a permission prompt, check the wiki and project settings for approved commands. The wiki documents which commands are pre-approved and how to invoke them. Unnecessary permission prompts interrupt the user's flow.

package/skills/simpleapps/project-defaults/SKILL.md

@@ -100,6 +100,11 @@ Two scopes, project overrides user:
 
 Resolution: read `{project}/.simpleapps/settings.json` first, fall back to `~/.simpleapps/settings.json`, fall back to defaults. Field-level override: project wins for any field it defines.
 
+Optional project-scoped fields:
+
+- `wikiTokenBudget` (number): override the 20K default wiki token budget. Set by `/curate-wiki` when the user approves an exception.
+- `wikiTokenBudgetReason` (string): why the budget was raised. Surfaced at the top of every `/curate-wiki` and `/wiki-audit` run so the exception stays visible and re-negotiable.
+
 ### site.json
 
 One per client project. Consistent structure across all sites: same fields, different values. Replaces the old `{siteId}.json` pattern.
@@ -172,7 +177,9 @@ Every project SHOULD configure `.claude/settings.local.json` with these deny rul
       "Bash(rg:*)",
       "Bash(sed:*)",
       "Bash(sleep:*)",
-      "Bash(tail:*)"
+      "Bash(tail:*)",
+      "Edit(~/.claude/plugins/**)",
+      "Write(~/.claude/plugins/**)"
     ]
   }
 }
@@ -191,6 +198,7 @@ Why each is denied:
 - **`rg`**: Use the Grep tool instead (it uses ripgrep internally).
 - **`sed`**: Use the Edit tool instead.
 - **`sleep`**: Unnecessary; use proper sequencing or background tasks.
+- **`Edit(~/.claude/plugins/**)` / `Write(~/.claude/plugins/**)`**: The installed plugin tree is a cache. Marketplace updates clobber it. To change plugin behavior, edit the plugin's source repo (e.g., `~/projects/simpleapps/augur-skills/`) instead.
 
 ## Bin Scripts (PATH)
 

package/skills/simpleapps/quality/SKILL.md

@@ -47,6 +47,31 @@ Missing quality tooling:
 
 Do not install or configure tools without the user's approval. Flag what's missing and explain why it helps. Let the user decide.
 
+## Runtime Freshness
+
+Projects SHOULD target the current Active LTS of their language runtime. Maintenance LTS is acceptable. EOL runtimes SHOULD be flagged.
+
+Runtime freshness is advisory, not a hard failure. Legitimate exceptions exist: libraries with documented compatibility policies, hosting-locked client projects, migration-in-progress repos. Surface findings as a prompt and let the user decide.
+
+Check the current LTS from the language's official schedule, not memory (LTS designations rotate each October):
+
+- Node: https://nodejs.org/en/about/previous-releases
+- Python: https://devguide.python.org/versions/
+- PHP: https://www.php.net/supported-versions.php
+
+### Where to check
+
+- CI matrices in `.github/workflows/*.yml`
+- `engines` in `package.json`
+- `python_requires` in `pyproject.toml` / `setup.py`
+- `require` or `config.platform.php` in `composer.json`
+
+### Prompt template
+
+> "CI matrix includes Node 18 (EOL). Current Active LTS is Node 24. Drop EOL and add current LTS?"
+
+If the user cites a constraint (hosting, compatibility, library support policy), record it in the project's wiki so future sessions see the exception and skip the prompt.
+
 ## When to suggest
 
 - **Setting up a new project**: suggest the full set
@@ -54,6 +79,7 @@ Do not install or configure tools without the user's approval. Flag what's missi
 - **Seeing inconsistent formatting**: suggest prettier
 - **No tests for changed code**: suggest vitest
 - **No pre-commit hooks**: suggest lefthook
+- **CI matrix or `engines` pins an EOL runtime**: suggest dropping it and adding current Active LTS
 
 ## Fix everything, hide nothing
 

package/skills/simpleapps/wiki/SKILL.md

@@ -21,14 +21,16 @@ The wiki is a **git-backed markdown folder** (`wiki/`) living next to the code r
 - **Markdown in git**: the docs live where the work lives and version alongside the code. Diffs show what changed and why. No login, no API, no stale snapshot.
 - **Separate `wiki/` repo, not embedded in the code repo**: the wiki ships independently of code releases. Doc fixes do not wait on code review cycles, and code commits stay clean of doc noise.
 - **Local file reads, not network fetches**: the agent loads the full wiki at session start with zero latency. No rate limits, no auth, works offline.
-- **20K token budget**: small enough to fit the whole wiki in context while leaving 90% for working memory. Forces ruthless editing; a 200K-token wiki that cannot be loaded helps no one.
+- **20K token budget**: small enough that the agent holds the whole wiki alongside working context with room to spare, and small enough that humans actually read and maintain it. Forces ruthless editing; a bloated wiki helps no one because no one reads past the first screen.
 - **Process and principles, not code snippets**: code in the wiki rots the day it is pasted. Link to the source file instead, so the wiki stays true as the code evolves.
 
 The payoff: **the agent and the user share the same model of the project.** Less re-explaining, fewer guesses, fewer "I assumed..." mistakes. Work goes faster because the agent already knows the conventions, and safer because the agent is not improvising decisions the wiki already settled.
 
 ## Token Budget
 
-A wiki MUST NOT exceed **20K tokens** (~15K words, ~60KB). This is 10% of the AI agent's 200K context window, enough for the agent to load the entire wiki at session start while leaving 90% for working context.
+The default wiki budget is **20K tokens** (~15K words, ~60KB). The budget is an editing constraint, not a capacity limit. It is small enough that agents load the whole wiki alongside working context with room to spare, small enough that humans actually read and maintain it, and strict enough to force pruning as the project grows.
+
+Projects MAY raise the budget via `wikiTokenBudget` in `.simpleapps/settings.json` when there is a documented reason (e.g., large integration catalogs, extensive cross-project references). Increases MUST be paired with a `wikiTokenBudgetReason` so future sessions see why the exception exists and can re-negotiate it. `/curate-wiki` handles the prompt and records the change. Never raise the budget silently.
 
 Check size: `wc -w wiki/*.md` (multiply by ~1.3 for token estimate)