@simpleapps-com/augur-skills 2026.3.28 → 2026.3.30
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
|
@@ -137,6 +137,10 @@ Every project SHOULD configure `.claude/settings.local.json` with these deny rul
|
|
|
137
137
|
|
|
138
138
|
```json
|
|
139
139
|
{
|
|
140
|
+
"env": {
|
|
141
|
+
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1",
|
|
142
|
+
"CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY": "1"
|
|
143
|
+
},
|
|
140
144
|
"permissions": {
|
|
141
145
|
"allow": [
|
|
142
146
|
"Bash(pnpm:*)",
|
|
@@ -77,6 +77,12 @@ If a rule or test seems wrong, investigate why it exists before concluding it sh
|
|
|
77
77
|
|
|
78
78
|
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.
|
|
79
79
|
|
|
80
|
+
## pnpm lockfile sync
|
|
81
|
+
|
|
82
|
+
In pnpm workspace projects, the root `pnpm-lock.yaml` and site-level lockfiles MUST stay in sync. CI uses `--frozen-lockfile` and will reject mismatched lockfiles — this is the most common cause of deploy failures.
|
|
83
|
+
|
|
84
|
+
After ANY `pnpm install`, `pnpm update`, or `pnpm add` in a workspace, run `pnpm install` at the repo root to regenerate the root lockfile. Commit both lockfiles together. If you forget, the next deploy will fail.
|
|
85
|
+
|
|
80
86
|
## Browser Error Overlays
|
|
81
87
|
|
|
82
88
|
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.
|