@simpleapps-com/augur-skills 2026.4.4 → 2026.4.6
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
|
@@ -72,6 +72,16 @@ MUST NOT use `kill` or `pkill` to stop background tasks — these are denied and
|
|
|
72
72
|
|
|
73
73
|
If a process was started **outside your session** (by the user in a terminal), you cannot stop it with `TaskStop`. Ask the user to restart or stop it themselves.
|
|
74
74
|
|
|
75
|
+
### Port conflicts (EADDRINUSE)
|
|
76
|
+
|
|
77
|
+
When a dev server fails with EADDRINUSE, a process from a previous session is occupying the port. Follow this sequence:
|
|
78
|
+
|
|
79
|
+
1. Check `TaskList` — if the task is listed, use `TaskStop`
|
|
80
|
+
2. If `TaskList` is empty, the process is from outside your session — ask the user: "Port N is in use by a process from a previous session. Can you stop it?"
|
|
81
|
+
3. MUST NOT attempt `kill`, `pkill`, or ask for permission to kill — these are denied and waste turns
|
|
82
|
+
|
|
83
|
+
Do not retry the server start until the user confirms the port is free.
|
|
84
|
+
|
|
75
85
|
## Cross-Project Searching
|
|
76
86
|
|
|
77
87
|
When looking at another project's code, use dedicated tools with the project path — MUST NOT use shell commands:
|
|
@@ -26,6 +26,8 @@ All projects live under `~/projects/` in two groups:
|
|
|
26
26
|
- Client site repos go in `~/projects/clients/`
|
|
27
27
|
- Workspace files go in `~/projects/workspaces/` — one `.code-workspace` per project
|
|
28
28
|
|
|
29
|
+
macOS APFS is case-insensitive by default. `~/Projects/` and `~/projects/` resolve to the same directory. Do NOT flag path casing differences as errors — only flag paths that genuinely do not resolve.
|
|
30
|
+
|
|
29
31
|
## Project Directory Layout
|
|
30
32
|
|
|
31
33
|
Every project MUST use this layout:
|
|
@@ -68,10 +68,11 @@ Applies to JSON arrays, markdown bullet lists, table rows, and any unordered col
|
|
|
68
68
|
|
|
69
69
|
## Code Style
|
|
70
70
|
|
|
71
|
-
Use descriptive variable and function names. Abbreviations save keystrokes but cost readability — the human reviewing your output MUST be able to understand the code without deciphering names.
|
|
71
|
+
Use descriptive variable and function names. Abbreviations save keystrokes but cost readability — the human reviewing your output MUST be able to understand the code without deciphering names. Short names also collide with terminology in the surrounding conversation and confuse the reader (e.g. using `p` as a path variable while the discussion is about a payment path — the reader will read `p` as "payment", not "path").
|
|
72
72
|
|
|
73
|
-
- MUST use full words: `$groupQuantity` not `$gq`, `cartItem` not `ci`
|
|
74
|
-
-
|
|
73
|
+
- MUST use full words: `$groupQuantity` not `$gq`, `cartItem` not `ci`, `filePath` not `p`, `response` not `r`
|
|
74
|
+
- MUST NOT use single-letter variable names except loop counters (`i`, `j`, `k`)
|
|
75
|
+
- Well-known abbreviations (`id`, `url`, `db`) are fine
|
|
75
76
|
- Function names SHOULD describe what they do: `calculateShippingCost` not `calcShip`
|
|
76
77
|
|
|
77
78
|
## Claude Code Keywords
|