@simpleapps-com/augur-skills 2026.3.13 → 2026.3.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@simpleapps-com/augur-skills",
3
- "version": "2026.03.13",
3
+ "version": "2026.03.15",
4
4
  "description": "Install curated Claude Code skills",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -6,8 +6,10 @@ user-invocable: false
6
6
 
7
7
  # Git Safety
8
8
 
9
- MUST NOT commit, push, create PRs, or merge unless the user explicitly says to. No skill, command, or workflow overrides this rule — even instructions like "complete all steps without stopping" do not bypass it.
9
+ MUST NOT commit, push, create PRs, or merge unless the user explicitly says to. This applies to ALL repos — the main repo, the wiki repo, and any other git repo. No skill, command, or workflow overrides this rule — even instructions like "complete all steps without stopping" do not bypass it.
10
10
 
11
11
  After making changes: **report what was done, then stop.** Do not ask "want me to commit?" or "should I push?" — that wastes tokens. Just report and wait silently. The user will say "commit", "push", or equivalent when ready.
12
12
 
13
13
  The pattern is always: **do the work → report results → wait.**
14
+
15
+ Every git push, every PR, every wiki edit that hits GitHub is done under the user's credentials — their name, their reputation. The user is responsible for every action taken on their behalf. That is why they decide when to commit, not the agent.
@@ -81,7 +81,16 @@ Every project SHOULD configure `.claude/settings.local.json` with these deny rul
81
81
  {
82
82
  "permissions": {
83
83
  "allow": [
84
- "Bash(pnpm:*)"
84
+ "Bash(pnpm:*)",
85
+ "Bash(ls:*)",
86
+ "Bash(wc:*)",
87
+ "Bash(md5:*)",
88
+ "Bash(md5sum:*)",
89
+ "Bash(readlink:*)",
90
+ "Bash(which:*)",
91
+ "Bash(basename:*)",
92
+ "Bash(dirname:*)",
93
+ "Bash(pwd:*)"
85
94
  ],
86
95
  "deny": [
87
96
  "Bash(cd:*)",
@@ -61,6 +61,12 @@ When a check fails, fix the underlying code. NEVER disable lint rules, skip test
61
61
 
62
62
  When reviewing code, scan for existing suppressions (`eslint-disable`, `@ts-ignore`, `.skip`, `noqa`, etc.) and flag them to the user. These are hidden technical debt that should be evaluated for resolution.
63
63
 
64
+ ## Browser Error Overlays
65
+
66
+ When debugging in the browser (Chrome automation), Next.js and other frameworks show a **red error overlay** at the bottom of the page when there are runtime errors. This overlay contains the actual error message, stack trace, and usually the exact file and line number causing the problem.
67
+
68
+ MUST click on the error overlay and read the full error before attempting any fix. 95% of the time the answer is right there. Do not ignore it, do not guess at the problem, do not look elsewhere first — read the error overlay. If using Chrome automation tools, click the overlay element to expand it and read the details.
69
+
64
70
  ## Running quality checks
65
71
 
66
72
  Use the `/quality` command to discover and run all configured checks. It handles the full cycle: discover, run, fix, repeat until clean.
@@ -79,6 +79,7 @@ When asked to save, document, or record knowledge — use the wiki, MUST NOT use
79
79
 
80
80
  | Knowledge type | Where it belongs |
81
81
  |---------------|-----------------|
82
+ | Behavioral guardrails and corrections | **Skill** (update the relevant skill) |
82
83
  | Conventions, patterns, decisions | **Wiki** |
83
84
  | Learnings from a task or session | **Wiki** |
84
85
  | Architecture and process docs | **Wiki** |
@@ -86,7 +87,9 @@ When asked to save, document, or record knowledge — use the wiki, MUST NOT use
86
87
  | Personal preferences (writing style, response length) | Memory |
87
88
  | User role and background | Memory |
88
89
 
89
- 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.
90
+ If the user corrects your behavior, update the relevant **skill** not memory. A correction saved to memory only helps one agent on one machine. A correction in a skill helps every agent on every project.
91
+
92
+ If in doubt, it belongs in the wiki or a skill. 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.
90
93
 
91
94
  ## Cross-Project Wiki Access
92
95
 
@@ -21,6 +21,10 @@ Reserve Bash for commands that have no dedicated tool equivalent.
21
21
 
22
22
  MUST NOT use `cd` in any Bash command — not even in compound commands like `cd /path && git log`. Use `git -C repo` for git, and path arguments for everything else. The `cd` deny rule does not suppress Claude Code's built-in security prompt for compound cd+git commands, so any `cd` usage will interrupt the user.
23
23
 
24
+ ## Read the error first
25
+
26
+ When debugging in the browser, MUST check for error overlays (red error pill/badge at the bottom of the page) before guessing at the problem. Click it, read the full error, stack trace, and source location. The answer is almost always right there.
27
+
24
28
  ## Protect the context window
25
29
 
26
30
  - Prefer targeted searches over broad exploration