@simpleapps-com/augur-skills 2026.3.11 → 2026.3.13

package/package.json

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

package/skills/simpleapps/augur-packages/SKILL.md

@@ -19,7 +19,7 @@ This skill is a **stub, not an archive**. New packages are created, existing pac
 
 **Always read the installed packages in your project's `node_modules/`:**
 
-1. Run `ls repo/node_modules/@simpleapps-com/` to discover ALL available packages — there may be packages not listed here
+1. Use `Glob("repo/node_modules/@simpleapps-com/*")` to discover ALL available packages — there may be packages not listed here
 2. Read `repo/node_modules/@simpleapps-com/<package>/package.json` for the `exports` field to find available sub-paths
 3. Read files in `repo/node_modules/@simpleapps-com/<package>/dist/` to understand the current API surface
 4. Do NOT look at the source repo or other folders — only read what is installed in your project's `node_modules/`
@@ -42,7 +42,7 @@ These are starting hints — not a complete list. Always check `node_modules/@si
 
 When considering custom code:
 
-1. Run `ls repo/node_modules/@simpleapps-com/` to see what's installed
+1. Use `Glob("repo/node_modules/@simpleapps-com/*")` to see what's installed
 2. Read the package's `package.json` `exports` and its `dist/` files for available functions, hooks, and components
 3. Look for the hook triple pattern in augur-hooks: `use<Name>`, `get<Name>Options`, `get<Name>Key`
 4. Check augur-web for UI components before building custom ones
@@ -70,10 +70,14 @@ The augur packages exist to share common code across ALL Node projects. When you
 
 The goal is to grow the packages over time so sites write less custom code.
 
+## augur-doctor
+
+`augur-doctor` ships with `@simpleapps-com/augur-config`. It checks version alignment, latest versions, and platform standard conformance. Run via `pnpm augur-doctor .` from the site directory — pre-approved, no permission prompt. For full documentation, see the augur-packages wiki page `guide-site-assessment.md` (use the cross-project wiki path from `simpleapps:wiki`).
+
 ## Platform Standards
 
 - **Icons:** `react-icons/lu`
 - **Tailwind:** v4, CSS-first
 - **Validation:** Valibot (not Zod, not Yup)
 - **Auth:** NextAuth 5 via package auth factory
-- **Reference site:** ampro-online
+- **Reference site:** Ask the user which site to reference. Use `Grep`, `Glob`, and `Read` with the project path (see `simpleapps:project-defaults` for layout). MUST NOT use `find`, `grep`, or other shell commands.

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

@@ -6,6 +6,10 @@ user-invocable: false
 
 # Bash Simplicity
 
+## Why This Matters
+
+Every permission prompt makes the user the bottleneck. If the user doesn't see the prompt for an hour, that hour is lost — the agent is blocked, the task stalls, and the system designed for autonomous work stops working. The entire plugin system exists to remove the user as the bottleneck. A permission prompt works directly against that goal. Use dedicated tools and simple commands to avoid ever triggering one.
+
 ## One Command Per Call
 
 MUST run each Bash command as a separate, simple call. MUST NOT chain commands with `&&`, `||`, pipes, or sub-shells. Complex commands trigger permission prompts and break automation.
@@ -13,8 +17,15 @@ MUST run each Bash command as a separate, simple call. MUST NOT chain commands w
 Wrong: `git -C repo status && pnpm typecheck && pnpm test`
 Right: Three separate Bash calls, one per command.
 
-Wrong: `pnpm --filter ampro-online run typecheck 2>&1; echo "EXIT: $?"`
-Right: `pnpm --filter ampro-online run typecheck` — the Bash tool already captures stderr and exit codes. Never add `2>&1`, `; echo $?`, or other shell plumbing — it triggers permission prompts for no benefit.
+Wrong: `pnpm --filter <site> run typecheck 2>&1; echo "EXIT: $?"`
+Right: `pnpm --filter <site> run typecheck` — the Bash tool already captures stderr and exit codes. Never add `2>&1`, `; echo $?`, or other shell plumbing — it triggers permission prompts for no benefit.
+
+Wrong: `gh issue close 367 --repo org/repo --comment "$(< tmp/file.txt)" 2>&1`
+Right: Write the comment to a tmp file, then use two separate calls:
+1. `gh issue comment 367 --repo org/repo --body-file tmp/file.txt`
+2. `gh issue close 367 --repo org/repo`
+
+MUST NOT use `$()` command substitution in Bash commands — it triggers a permission prompt every time. Write content to a tmp file first, then pass it with a `-F`, `--body-file`, or similar flag.
 
 ## Use Dedicated Tools
 
@@ -33,6 +44,22 @@ Reserve Bash for commands that have no dedicated tool equivalent: build tools, t
 These commands are **denied** in project settings and will always be rejected — do not attempt them:
 `cd`, `cat`, `grep`, `rg`, `find`, `sed`, `awk`, `head`, `tail`, `sleep`, `kill`, `pkill`
 
+MUST NOT use `node -e` or `python -c` to run inline scripts — these trigger permission prompts. If you need to read a file, use the Read tool. If you need to process data, do it in your response, not in a shell script.
+
+## Cross-Project Searching
+
+When looking at another project's code, use dedicated tools with the project path — MUST NOT use shell commands:
+
+Wrong: `find {path}/repo -name "*.ts" -exec grep -l "pattern" {} \; 2>/dev/null | head -10`
+Right: `Grep(pattern: "pattern", path: "{path}/repo", glob: "*.ts")`
+
+Wrong: `ls {path}/repo/src/components/`
+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.
+
 ## 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.
+
+**`pnpm:*` is pre-approved** — any command in `package.json` scripts runs without permission via `pnpm <script>`. If a tool needs to run repeatedly (linters, formatters, test runners), it SHOULD be a `package.json` script so it can run via pnpm without prompting. Suggest adding missing scripts when you notice the gap.

package/skills/simpleapps/github/SKILL.md

@@ -61,6 +61,8 @@ This avoids shell quoting issues with HEREDOCs and `cd` permission blocks. The W
 
 MUST use `--repo simpleapps-com/<repo>` on every `gh` call. MUST ask the user which repo — never assume.
 
+**MUST NOT use `$()` or inline content in `gh` commands.** Any `gh` command that needs a body, comment, or multi-line text MUST use the file-based flag (`--body-file`, `--comment-file`, etc.). Write the content to `tmp/` using the Write tool first, then pass the file path. This avoids `$()` command substitution which triggers a permission prompt every time. Delete the tmp file after the command succeeds.
+
 ### Title
 
 Conventional commit style: `fix: description`, `feat: description`, `chore: description`. Under 70 characters.
@@ -89,9 +91,14 @@ Bug reports also include **Steps to Reproduce** and **Current Behavior** with er
 gh issue create --repo simpleapps-com/<repo> --title "type: desc" --body "..."
 gh issue list --repo simpleapps-com/<repo>
 gh issue view <number> --repo simpleapps-com/<repo>
-gh issue close <number> --repo simpleapps-com/<repo> --comment "message"
+gh issue close <number> --repo simpleapps-com/<repo>
 ```
 
+For closing with a comment, use two calls (avoids `$()` permission prompts):
+1. Write comment to `tmp/issue-comment.txt` using the Write tool
+2. `gh issue comment <number> --repo simpleapps-com/<repo> --body-file tmp/issue-comment.txt`
+3. `gh issue close <number> --repo simpleapps-com/<repo>`
+
 Include `Closes #N` in commit body to auto-close issues.
 
 ### Commenting on existing issues
@@ -115,17 +122,19 @@ Target repos:
 | Shared frontend packages | `simpleapps-com/augur-packages` |
 | TypeScript API SDK | `simpleapps-com/augur-api` |
 
-Example cross-link in issue body: `Upstream: simpleapps-com/augur#44` or `Local impact: simpleapps-com/spotweldingsupplies#3`
+Example cross-link in issue body: `Upstream: simpleapps-com/augur#44` or `Local impact: simpleapps-com/<site>#3`
 
 ## Pull Requests
 
 ```bash
-gh pr create --repo simpleapps-com/<repo> --title "title" --body "..."
+gh pr create --repo simpleapps-com/<repo> --title "title" --body-file tmp/pr-body.txt
 gh pr list --repo simpleapps-com/<repo>
 gh pr view <number> --repo simpleapps-com/<repo>
 gh pr merge <number> --repo simpleapps-com/<repo>
 ```
 
+Write PR body to `tmp/pr-body.txt` using the Write tool first — MUST NOT use `--body "$(cat ...)"` or any `$()` substitution.
+
 ## Cross-Linking with Basecamp
 
 For client tasks originating in Basecamp, see `simpleapps:workflow` for the full cross-linking process.

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

@@ -15,12 +15,9 @@ All projects live under `~/projects/` in two groups:
 ```
 ~/projects/
 ├── simpleapps/          # Internal repos (augur-*, shared infra)
-│   ├── augur-skills/
-│   ├── augur-packages/
-│   └── augur/
+│   └── <repo-name>/
 └── clients/             # Client site repos
-    ├── ampro-online/
-    └── directsupplyinc/
+    └── <site-name>/
 ```
 
 - Internal repos go in `~/projects/simpleapps/`

package/skills/simpleapps/wiki/SKILL.md

@@ -88,6 +88,20 @@ When asked to save, document, or record knowledge — use the wiki, MUST NOT use
 
 If in doubt, it belongs in the wiki. The cost of putting shared knowledge in memory is that it dies with the session — no other agent, project, or computer will ever see it.
 
+## Cross-Project Wiki Access
+
+All projects follow the same directory layout (see `simpleapps:project-defaults`). Every project's wiki is at a predictable path relative to the project root: `{project}/wiki/`. When the user asks you to check another project's wiki or code, use the project-defaults layout to find it.
+
+**Before reading another project's wiki, pull the latest:**
+`git -C {path-to-project}/wiki pull`
+
+**MUST use dedicated tools for cross-project access — MUST NOT use shell commands:**
+- Read files: `Read("{path-to-project}/wiki/Page.md")`
+- Search code: `Grep(pattern: "...", path: "{path-to-project}/repo")`
+- Find files: `Glob(pattern: "{path-to-project}/repo/**/*.ts")`
+
+MUST NOT use `find`, `grep`, `cat`, `ls`, or any shell command to explore other projects. The paths are known — use the dedicated tools directly.
+
 ## Keep It Lean
 
 - Document patterns and principles, not exhaustive lists