@simpleapps-com/augur-skills 2026.4.4 → 2026.4.5
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
|
@@ -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
|