@erclx/aitk 3.2.0 → 3.3.0
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,19 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Enforce the CLAUDE.md edit protocol and the test routing a fact into it rather than a rule
|
|
3
|
+
paths:
|
|
4
|
+
- 'CLAUDE.md'
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# CLAUDE.md standards
|
|
8
|
+
|
|
9
|
+
## Editing
|
|
10
|
+
|
|
11
|
+
- Show the proposed change as a fenced `diff` block in chat first, then wait for approval before calling the file-editing tool.
|
|
12
|
+
|
|
13
|
+
## Routing
|
|
14
|
+
|
|
15
|
+
- Keep a rule here when it applies every session regardless of what is being edited.
|
|
16
|
+
- Move a rule into `.claude/rules/` when it fires only on a specific path being edited and violating it ships silently.
|
|
17
|
+
- Route a rule failing either half to a context entry or a skill body rather than here.
|
|
18
|
+
- Name a rule's tier rather than a rule file. A path-scoped rule reaches the session on its own glob and needs no pointer from here.
|
|
19
|
+
- Point at a skill by name where one applies. A skill loads only when invoked, so an unreferenced skill is one no session finds.
|
package/package.json
CHANGED
|
@@ -43,6 +43,16 @@ A decision's reasoning stays correct while the numbers it cites move. The anchor
|
|
|
43
43
|
- Do not edit a claim in the pass that first anchors it. The anchor states what the claim was measured against, so changing both at once leaves nothing to check the anchor against.
|
|
44
44
|
- Refresh the anchor whenever the number is re-read, whether or not it moved. A confirmed number and an unread one are the same text without the date.
|
|
45
45
|
|
|
46
|
+
## Length
|
|
47
|
+
|
|
48
|
+
Every session pays for this file before any work starts, so it carries a budget. The budget counts decisions rather than lines, because a bare line total is satisfied by merging paragraph pairs and the merged paragraphs then fail the weight checkpoint in `markdown.md`. A file over budget is carrying too many decisions, not decisions written too long.
|
|
49
|
+
|
|
50
|
+
- Budget six lines per decision entry, being the H3, two paragraphs, and the blank lines separating them.
|
|
51
|
+
- Budget the frame outside `## Key technical decisions` separately, covering the H1, the overview, and the risks. State the number the project takes where it records the budget, since a frame carries no fixed structure to derive one from.
|
|
52
|
+
- Read the ceiling as the frame plus six lines against the decision count, rather than as the total the two multiply out to.
|
|
53
|
+
- Bring an over-budget file back by merging two decisions or retiring one, never by compressing a decision's prose.
|
|
54
|
+
- Yield the budget to the paragraph weight checkpoint when the two disagree. A paragraph past the checkpoint is a defect no budget licenses.
|
|
55
|
+
|
|
46
56
|
## Template
|
|
47
57
|
|
|
48
58
|
The anchor sentence closes a decision whose reasoning cites a measured number and is absent from one that cites none.
|
|
@@ -22,6 +22,7 @@
|
|
|
22
22
|
- Do not add features the user did not ask for
|
|
23
23
|
- When rewriting a section, preserve existing code blocks, tables, and grouped examples unless the user asked to remove them
|
|
24
24
|
- When planning an edit to `CLAUDE.md`, show the proposed change as a fenced `diff` block in chat first, then wait for approval before calling `Edit`
|
|
25
|
+
- Keep a rule in `CLAUDE.md` when it applies every session regardless of what is being edited. Move one that fires only on a specific path being edited and ships silently when violated into `.claude/rules/`.
|
|
25
26
|
- Edit an existing file with the file-editing tool, never a shell stream editor. An unescaped `&` in a `sed` replacement expands to the whole match, and `sed -i` exits zero when its pattern matches nothing, so both fail silently while reporting success. This governs edits you make, not stream editors written into a project's own scripts.
|
|
26
27
|
|
|
27
28
|
## Indexes
|