claude-dev-env 8.72.1 → 8.72.2
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.
|
@@ -28,6 +28,7 @@ definitions and dictionary decisions.
|
|
|
28
28
|
- Use inclusive, neutral language.
|
|
29
29
|
- Use periods, commas, colons, and bullets to show structure.
|
|
30
30
|
- Preserve exact quoted labels, identifiers, formulas, titles, and interface text.
|
|
31
|
+
- Say each fact once in content read together. Preserve accessible text alternatives for pictures and essential prerequisites or warnings at each point of use.
|
|
31
32
|
- Send the reader only a result, a blocker, or a question. Leave out a line that says nothing is needed from them, and leave out which agent, session, or coordinator did the work.
|
|
32
33
|
- Use `WARNING` for a risk of injury or death. Use `CAUTION` for a risk of equipment, tool, or machine damage. State the command or condition first, then state the result.
|
|
33
34
|
- Aim for 20 words or fewer in a procedure sentence when the technical content allows.
|
|
@@ -38,5 +39,14 @@ and durable repository text. Named contracts can add behavior-specific structure
|
|
|
38
39
|
question routing, current-state documentation, completion, docstring, or publication rules.
|
|
39
40
|
Those contracts use this policy for their language.
|
|
40
41
|
|
|
42
|
+
## Repeated-points check
|
|
43
|
+
|
|
44
|
+
Run this check on each reply or page you draft, before you send it. Run it also when asked to check text for repeated points.
|
|
45
|
+
|
|
46
|
+
1. List each fact the text states, with where it appears. Include each fact that a picture, diagram, or table shows: its labels, its order, what moves, and the end state it draws.
|
|
47
|
+
2. Mark repeated facts within content read together. Exclude accessibility text, alternate representations, and prerequisites or warnings needed at each point of use.
|
|
48
|
+
3. Keep each marked fact in the one place that shows it best. Delete each other statement of it, or rewrite that line to carry a new fact. Outside these exceptions, a bullet under a picture keeps only what the picture cannot show, such as a cause, a condition, a command, or a warning.
|
|
49
|
+
4. Keep routine self-check results silent. When asked to review repeated points, report each restatement you removed, or report that each fact appears once.
|
|
50
|
+
|
|
41
51
|
Treat automated output and language checks as drafting aids. A responsible human verifies
|
|
42
52
|
technical accuracy, terminology, safety, confidentiality, and intended meaning.
|
package/package.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
**When:** Writing chat, tool narration, or repository prose.
|
|
4
4
|
|
|
5
|
-
Use the sole general language rule. Write short, complete sentences on one topic. Use active voice; lead with conditions;
|
|
5
|
+
Use the sole general language rule. Write short, complete sentences on one topic. Use active voice; lead with conditions; one action per step. Use plain, precise words, stable terms. Expand abbreviations and contractions; name unclear pronouns. Be inclusive; punctuate clearly. Preserve exact labels, identifiers, formulas, titles, interface text. Say each fact once. Send a result, blocker, or question. Mark injury or death `WARNING`, equipment damage `CAUTION`; state condition then result. Aim for 20 words per step, 25 per description. Treat checks as aids; have a human verify accuracy, terms, safety, confidentiality, meaning.
|
|
6
6
|
|
|
7
7
|
**Enforcement:** none.
|
|
8
8
|
|