@simpleapps-com/augur-skills 2026.3.22 → 2026.3.23

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.22",
3
+ "version": "2026.03.23",
4
4
  "description": "Install curated Claude Code skills",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -57,9 +57,19 @@ Do not install or configure tools without the user's approval. Flag what's missi
57
57
 
58
58
  ## Resolve, never hide
59
59
 
60
- When a check fails, fix the underlying code. NEVER disable lint rules, skip tests, suppress warnings, lower thresholds, or add ignore comments to make checks pass. The goal is to resolve issues, not hide them. If a rule seems wrong, investigate why it exists and ask the user before changing it.
60
+ When a check fails, the solution is ALWAYS to fix the underlying code. NEVER:
61
61
 
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.
62
+ - Disable or weaken a lint rule (`eslint-disable`, rule removal, config changes)
63
+ - Skip or delete a failing test (`.skip`, `.only`, deleting the test)
64
+ - Silence type errors (`@ts-ignore`, `@ts-expect-error`, `type: any`)
65
+ - Suppress warnings, lower coverage thresholds, or modify quality configs
66
+ - Add `--no-verify`, `--force`, or flags that bypass checks
67
+
68
+ These actions hide problems — they do not fix them. A suppressed error is worse than a visible one because it will be forgotten and compound.
69
+
70
+ If a rule or test seems wrong, investigate why it exists before concluding it should change. Rules exist for reasons. If after investigation it genuinely does not apply, explain the reasoning to the user and let them decide — do not unilaterally disable it.
71
+
72
+ When reviewing code, scan for existing suppressions (`eslint-disable`, `@ts-ignore`, `.skip`, `noqa`, `phpcs:ignore`, etc.) and flag every instance to the user. These are hidden technical debt.
63
73
 
64
74
  ## Browser Error Overlays
65
75