rhachet-roles-ehmpathy 1.17.21 → 1.17.22
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.
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
### .rule = forbid-buzzwords
|
|
2
|
+
|
|
3
|
+
#### .what
|
|
4
|
+
buzzwords must be avoided — they obscure intent
|
|
5
|
+
|
|
6
|
+
#### .scope
|
|
7
|
+
- code: variable names, function names, type names, comments
|
|
8
|
+
- docs: markdown, briefs, prompts, commit messages
|
|
9
|
+
- comms: pr descriptions, reviews, discussions
|
|
10
|
+
|
|
11
|
+
#### .why
|
|
12
|
+
buzzwords have **large gravity** — they pull the mind toward them
|
|
13
|
+
|
|
14
|
+
this gravity causes **semantic diffusion**:
|
|
15
|
+
- the word feels meaningful, so thought stops
|
|
16
|
+
- precision erodes because the term is overloaded
|
|
17
|
+
- ambiguity creeps in because everyone maps it to their own interpretation
|
|
18
|
+
- communication degrades because we think we agree when we don't
|
|
19
|
+
|
|
20
|
+
it's a smell. flies buzz around smells. we don't like smells -> we dont like buzz.
|
|
21
|
+
|
|
22
|
+
#### .instead
|
|
23
|
+
think from the core. build the concept from the ground up.
|
|
24
|
+
|
|
25
|
+
find the most appropriate non-buzz word:
|
|
26
|
+
- what specifically do you mean?
|
|
27
|
+
- what is the precise action, object, or attribute?
|
|
28
|
+
- what word captures exactly this, with no surplus baggage?
|
|
29
|
+
|
|
30
|
+
precision > familiarity. clarity > trendiness.
|
|
31
|
+
|
|
32
|
+
#### .enforcement
|
|
33
|
+
buzzwords = **BLOCKER** on first encounter. if retry with justification, allow.
|
|
34
|
+
|
|
35
|
+
#### .the test
|
|
36
|
+
if you remove the buzzword and the sentence still makes sense — you didn't need it.
|
|
37
|
+
if you replace it with a concrete term and meaning is preserved — use the concrete term.
|
|
38
|
+
if you can't replace it with anything concrete — you don't know what you mean yet.
|
|
39
|
+
|
|
40
|
+
#### .note: context matters
|
|
41
|
+
some terms are buzzwords in one context but precise in another:
|
|
42
|
+
- `scalable` in marketing = buzz
|
|
43
|
+
- `scalable` in distributed systems with defined semantics = maybe ok (but still prefer specifics)
|
|
44
|
+
|
|
45
|
+
when in doubt, be more specific.
|
|
46
|
+
|
|
47
|
+
#### .see also
|
|
48
|
+
- `rule.prefer.lowercase` — no shouts
|
|
49
|
+
- `rule.require.ubiqlang` — consistent terminology
|
package/package.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"name": "rhachet-roles-ehmpathy",
|
|
3
3
|
"author": "ehmpathy",
|
|
4
4
|
"description": "empathetic software construction roles and skills, via rhachet",
|
|
5
|
-
"version": "1.17.
|
|
5
|
+
"version": "1.17.22",
|
|
6
6
|
"repository": "ehmpathy/rhachet-roles-ehmpathy",
|
|
7
7
|
"homepage": "https://github.com/ehmpathy/rhachet-roles-ehmpathy",
|
|
8
8
|
"keywords": [
|
|
@@ -52,7 +52,7 @@
|
|
|
52
52
|
"prepare:husky": "husky install && chmod ug+x .husky/*",
|
|
53
53
|
"prepare": "if [ -e .git ] && [ -z $CI ]; then npm run prepare:husky && npm run prepare:rhachet; fi",
|
|
54
54
|
"test:format:biome": "biome format",
|
|
55
|
-
"prepare:rhachet": "rhachet init
|
|
55
|
+
"prepare:rhachet": "rhachet init --roles behaver mechanic reviewer"
|
|
56
56
|
},
|
|
57
57
|
"dependencies": {
|
|
58
58
|
"@ehmpathy/as-command": "1.0.3",
|