@noir-ai/create 1.16.0 → 1.17.0-beta.1

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": "@noir-ai/create",
3
- "version": "1.16.0",
3
+ "version": "1.17.0-beta.1",
4
4
  "description": "Noir scaffold engine — the idempotent declarative writer, manifest, templates, stack-detect, and migrations that power `noir init`/`create`/`sync`.",
5
5
  "license": "MIT",
6
6
  "author": "agaaaptr",
@@ -46,8 +46,8 @@
46
46
  "templates"
47
47
  ],
48
48
  "dependencies": {
49
- "@noir-ai/adapters": "1.16.0",
50
- "@noir-ai/core": "1.16.0"
49
+ "@noir-ai/adapters": "1.17.0-beta.1",
50
+ "@noir-ai/core": "1.17.0-beta.1"
51
51
  },
52
52
  "devDependencies": {
53
53
  "@types/node": "^22.17.0"
@@ -0,0 +1,50 @@
1
+ # Anti-slop rules
2
+
3
+ Plain, specific prose beats decorated prose. These rules catch the wording a
4
+ reader has to untangle before they can act on it.
5
+
6
+ ## Banned words
7
+
8
+ Prefer plain verbs and concrete nouns. Do not use: delve, utilize, leverage,
9
+ facilitate, elucidate, embark, endeavor, encompass, multifaceted, tapestry,
10
+ testament, paradigm, synergy, holistic, catalyze, juxtapose, realm, landscape,
11
+ myriad, plethora.
12
+
13
+ ## Rationed words
14
+
15
+ Use at most one of these per paragraph: robust, comprehensive, seamless,
16
+ cutting-edge, innovative, streamline, empower, foster, enhance, elevate, optimize,
17
+ scalable, pivotal, intricate, profound, resonate, underscore, navigate, cultivate,
18
+ bolster, galvanize, cornerstone, game-changer.
19
+
20
+ ## Filler and frame phrases
21
+
22
+ Delete filler phrases (it is important to note that, needless to say) and slop
23
+ trigrams (a testament to, in the realm of, serves as a). Write the claim, not the
24
+ frame around it.
25
+
26
+ ## Em-dashes and contrasts
27
+
28
+ Keep em-dashes to at most two per paragraph. Avoid the not-X-but-Y contrast: it
29
+ adds a fake turn without adding information.
30
+
31
+ ## The laziness ladder
32
+
33
+ Climb these rungs in order and stop at the first one that holds.
34
+
35
+ - **Does this need to exist?** A speculative need is a reason to skip it, not
36
+ build it.
37
+ - **Is it already here?** Reuse what the codebase has before writing anything
38
+ new.
39
+ - **Does the standard library do it?** Prefer it over a new dependency.
40
+ - **Does the platform do it?** A native feature beats a library that wraps it.
41
+ - **Can it be one line?** One line beats fifty.
42
+ - **Can it be deleted?** Removing code is a smaller change than adding code.
43
+ - **Fix the root cause, not the symptom.** Guard the shared path every caller
44
+ routes through, not the one caller a report names.
45
+
46
+ ## The noir-debt: marker
47
+
48
+ When you deliberately cut a corner with a known limit, leave a `noir-debt:`
49
+ marker in the code that names the ceiling and the upgrade trigger: the condition
50
+ that means the shortcut has stopped holding and the real fix is due.
@@ -26,7 +26,7 @@
26
26
  ## Output hygiene (run before claiming done)
27
27
  - Keep every comment, summary, and document to what a reader can act on: no decorative banners
28
28
  or dividers, no step-by-step narration of the code, no decorative emoji or icons. The
29
- `noir-code-hygiene` skill carries the full set of defects and their fixes.
29
+ `noir-codebase-audit` skill carries the full set of defects and their fixes.
30
30
  - Write in the project's own language: a character from another script, or an invisible one
31
31
  (a zero-width space, a byte-order mark, a bidirectional override, the replacement character
32
32
  a bad decode leaves), means the text was not written for this codebase.
@@ -40,3 +40,19 @@
40
40
  ## Conventions gotchas (project-specific — fill in)
41
41
  - Commits stay local until explicitly pushed.
42
42
  - The full test suite runs offline, with no network access and no paid API key.
43
+
44
+ ## Anti-slop
45
+
46
+ Prefer plain verbs and concrete nouns. Do not use: delve, utilize, leverage, facilitate,
47
+ elucidate, embark, endeavor, encompass, multifaceted, tapestry, testament, paradigm,
48
+ synergy, holistic, catalyze, juxtapose, realm, landscape, myriad, plethora.
49
+
50
+ Use at most one of these per paragraph: robust, comprehensive, seamless, cutting-edge,
51
+ innovative, streamline, empower, foster, enhance, elevate, optimize, scalable, pivotal,
52
+ intricate, profound, resonate, underscore, navigate, cultivate, bolster, galvanize,
53
+ cornerstone, game-changer.
54
+
55
+ Delete filler phrases (it is important to note that, needless to say) and slop trigrams
56
+ (a testament to, in the realm of, serves as a). Write the claim, not the frame.
57
+
58
+ Keep em-dashes to at most two per paragraph. Avoid the not-X-but-Y contrast.