@simpleapps-com/augur-skills 2026.4.1 → 2026.4.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@simpleapps-com/augur-skills",
-  "version": "2026.04.1",
+  "version": "2026.04.2",
   "description": "Install curated Claude Code skills",
   "license": "MIT",
   "type": "module",

package/skills/simpleapps/basecamp/SKILL.md

@@ -13,7 +13,7 @@ allowed-tools:
 
 IMPORTANT: MUST NOT create, edit, or delete anything in Basecamp without user permission.
 
-**Content format**: All write tools SHOULD use plain text with line breaks, NOT HTML. Basecamp returns HTML in responses but prefers plain text for creation.
+**Content format**: All write tools MUST use plain text with line breaks, NOT HTML. Basecamp returns HTML in responses but prefers plain text for creation.
 
 ## Setup
 

package/skills/simpleapps/deployment/SKILL.md

@@ -20,7 +20,7 @@ This skill reads the project's `wiki/Deployment.md` and executes the steps defin
 
 ## Deployment Page Format
 
-Every project wiki SHOULD have a `Deployment.md` page with up to three sections:
+Every project wiki MUST have a `Deployment.md` page with up to three sections:
 
 ```
 ## Submit

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

@@ -158,18 +158,19 @@ Every project SHOULD configure `.claude/settings.local.json` with these deny rul
       "mcp__plugin_simpleapps_augur-api__*"
     ],
     "deny": [
-      "Bash(cd:*)",
+      "Bash(awk:*)",
       "Bash(cat:*)",
-      "Bash(sed:*)",
+      "Bash(cd:*)",
+      "Bash(find:*)",
+      "Bash(for:*)",
       "Bash(grep:*)",
-      "Bash(sleep:*)",
+      "Bash(head:*)",
       "Bash(kill:*)",
       "Bash(pkill:*)",
-      "Bash(find:*)",
-      "Bash(head:*)",
-      "Bash(tail:*)",
-      "Bash(awk:*)",
-      "Bash(rg:*)"
+      "Bash(rg:*)",
+      "Bash(sed:*)",
+      "Bash(sleep:*)",
+      "Bash(tail:*)"
     ]
   }
 }
@@ -177,16 +178,17 @@ Every project SHOULD configure `.claude/settings.local.json` with these deny rul
 
 Why each is denied:
 
-- **`cd`** — MUST NOT use in any Bash command, including compound commands (`cd /path && git`). Use `git -C repo` for git, path arguments for everything else. Compound cd+git commands trigger an unblockable Claude Code security prompt that interrupts the user even when `cd` is denied.
+- **`awk`** — Use the Edit tool instead.
 - **`cat`** — Use the Read tool instead.
-- **`sed`** — Use the Edit tool instead.
-- **`grep`** — Use the Grep tool instead.
-- **`sleep`** — Unnecessary; use proper sequencing or background tasks.
+- **`cd`** — MUST NOT use in any Bash command, including compound commands (`cd /path && git`). Use `git -C repo` for git, path arguments for everything else. Compound cd+git commands trigger an unblockable Claude Code security prompt that interrupts the user even when `cd` is denied.
 - **`find`** — Use the Glob tool instead.
+- **`for`** — Shell loops are unnecessary; use dedicated tools or make multiple tool calls instead.
+- **`grep`** — Use the Grep tool instead.
 - **`head`/`tail`** — Use the Read tool with `offset` and `limit` parameters instead.
-- **`awk`** — Use the Edit tool instead.
+- **`kill`/`pkill`** — Use `TaskStop` to manage background processes. `TaskStop` cleanly shuts down the task and updates Claude Code's internal tracking.
 - **`rg`** — Use the Grep tool instead (it uses ripgrep internally).
-- **`kill`/`pkill`** — Use `TaskStop` to manage background processes. For internal tasks running in the background (dev servers, watchers, etc.), always use `TaskStop` instead of shell kill commands. `TaskStop` cleanly shuts down the task and updates Claude Code's internal tracking.
+- **`sed`** — Use the Edit tool instead.
+- **`sleep`** — Unnecessary; use proper sequencing or background tasks.
 
 ## Bin Scripts (PATH)
 

package/skills/simpleapps/wiki/SKILL.md

@@ -126,11 +126,11 @@ The wikis are kept fresh by `/curate-wiki` runs across projects. Searching local
 
 ## Deployment Page
 
-Every project wiki SHOULD have a `Deployment.md` page with up to three sections: Submit, Deploy, and Publish. This page defines the project-specific steps that `/submit`, `/deploy`, and `/publish` commands execute. Run `/curate-wiki` to generate it from the codebase — the command scans CI workflows, package.json, deploy scripts, and asks the user about anything it cannot determine. See the `deployment` skill for the expected format.
+Every project wiki MUST have a `Deployment.md` page with up to three sections: Submit, Deploy, and Publish. This page defines the project-specific steps that `/submit`, `/deploy`, and `/publish` commands execute. Run `/curate-wiki` to generate it from the codebase — the command scans CI workflows, package.json, deploy scripts, and asks the user about anything it cannot determine. See the `deployment` skill for the expected format.
 
 ## Testing Page
 
-Every project wiki SHOULD have a `Testing.md` page. This is the E2E verification checklist that `/verify` uses to walk through the site in Chrome. The page grows over time — `/curate-wiki` SHOULD add testing knowledge learned during the session (new edge cases, failure patterns, test data) to the Testing page.
+Every project wiki MUST have a `Testing.md` page. This is the E2E verification checklist that `/verify` uses to walk through the site in Chrome. The page grows over time — `/curate-wiki` MUST add testing knowledge learned during the session (new edge cases, failure patterns, test data) to the Testing page.
 
 A good Testing page covers: test tiers (automated vs manual), test data (items, accounts, cards), and an E2E checklist organized by page area (homepage, listing, detail, cart, checkout, etc.). Each checklist item is a concrete, verifiable condition — not vague ("works") but specific ("price shows $9.26").
 

package/skills/simpleapps/writing-style/SKILL.md

@@ -60,6 +60,12 @@ Every token costs time, money, and cognitive load. Be concise without losing cla
 
 Default to brief. Expand only when the reader cannot infer meaning from context. Two sentences that answer the question beat two pages that fill the context window.
 
+## List Ordering
+
+Lists with no inherent order (deny rules, config arrays, feature lists, bullet-point explanations) MUST be sorted alphabetically. Alphabetical order makes items easier to find and minimizes git diffs — new entries slot into a predictable position instead of appending at the end.
+
+Applies to JSON arrays, markdown bullet lists, table rows, and any unordered collection.
+
 ## Code Style
 
 Use descriptive variable and function names. Abbreviations save keystrokes but cost readability — the human reviewing your output MUST be able to understand the code without deciphering names.