@simpleapps-com/augur-skills 2026.3.12 → 2026.3.13

package/package.json

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

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

@@ -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 — use `Grep`, `Glob`, and `Read` with path `~/projects/clients/ampro-online/repo` to see how patterns are implemented. MUST NOT use `find`, `grep`, or other shell commands.
+- **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

@@ -17,8 +17,8 @@ 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:
@@ -48,13 +48,13 @@ MUST NOT use `node -e` or `python -c` to run inline scripts — these trigger pe
 
 ## Cross-Project Searching
 
-When looking at another project's code (e.g., the reference site ampro-online), use dedicated tools with the known project path — MUST NOT use shell commands:
+When looking at another project's code, use dedicated tools with the project path — MUST NOT use shell commands:
 
-Wrong: `find ~/projects/clients/ampro-online/repo -name "*.ts" -exec grep -l "pattern" {} \; 2>/dev/null | head -10`
-Right: `Grep(pattern: "pattern", path: "~/projects/clients/ampro-online/repo", glob: "*.ts")`
+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 ~/projects/clients/ampro-online/repo/src/components/`
-Right: `Glob(pattern: "~/projects/clients/ampro-online/repo/src/components/**/*")`
+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.
 

package/skills/simpleapps/github/SKILL.md

@@ -122,7 +122,7 @@ 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
 

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

@@ -90,27 +90,15 @@ If in doubt, it belongs in the wiki. The cost of putting shared knowledge in mem
 
 ## Cross-Project Wiki Access
 
-All SimpleApps projects follow the same directory layout under `~/projects/`. Every project's wiki is at a known, predictable path:
-
-| Project type | Wiki path |
-|-------------|-----------|
-| Client sites | `~/projects/clients/<site-name>/wiki/` |
-| Internal repos | `~/projects/simpleapps/<repo-name>/wiki/` |
-
-**Reference site:** `~/projects/clients/ampro-online/` is the reference implementation. When you need to see how something was done, check its wiki and repo first.
-
-**Key wikis to consult:**
-- `~/projects/simpleapps/augur-packages/wiki/` — shared package conventions, API surfaces, component patterns
-- `~/projects/simpleapps/augur-skills/wiki/` — plugin and skill authoring conventions
-- `~/projects/clients/ampro-online/wiki/` — reference site patterns, real-world usage examples
+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 ~/projects/clients/<site>/wiki pull`
+`git -C {path-to-project}/wiki pull`
 
 **MUST use dedicated tools for cross-project access — MUST NOT use shell commands:**
-- Read files: `Read("~/projects/clients/<site>/wiki/Page.md")` or `Read("~/projects/clients/<site>/repo/path/to/file")`
-- Search code: `Grep(pattern: "...", path: "~/projects/clients/<site>/repo")`
-- Find files: `Glob(pattern: "~/projects/clients/<site>/repo/**/*.ts")`
+- 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.