toga-ai 1.0.799 → 1.0.800
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
|
@@ -51,6 +51,44 @@ What you need to do:
|
|
|
51
51
|
4. Confirm the WorkerJobs table shows the new column.
|
|
52
52
|
```
|
|
53
53
|
|
|
54
|
+
## Cut output tokens — the safe way
|
|
55
|
+
|
|
56
|
+
Shorter answers are clearer AND cheaper to run. Both matter. But **clarity always wins** —
|
|
57
|
+
every rule here stops the moment it would make you harder to understand. This sharpens the
|
|
58
|
+
rules above; it never overrides them.
|
|
59
|
+
|
|
60
|
+
**Drop these words — they add length, not meaning:**
|
|
61
|
+
|
|
62
|
+
- Filler: just, really, basically, actually, simply.
|
|
63
|
+
- Pleasantries: sure, certainly, of course, happy to, great question.
|
|
64
|
+
- Hedging: I think, it seems, perhaps, kind of, sort of.
|
|
65
|
+
|
|
66
|
+
Say it straight. "Basically you just need to..." → "You need to...".
|
|
67
|
+
|
|
68
|
+
**Keep these exact — never shorten:**
|
|
69
|
+
|
|
70
|
+
- Numbers, and negation words: not, never, no, only, except. Flipping one changes the
|
|
71
|
+
meaning — never worth a saved word.
|
|
72
|
+
- Code, commands, file names, and error text — word for word. Do not compress or reword them.
|
|
73
|
+
|
|
74
|
+
**Do not narrate your tool use.** Skip "Now I'll read the file", "Let me check", "I'm going
|
|
75
|
+
to run...". Do the work, then report the result.
|
|
76
|
+
|
|
77
|
+
**Do not dump long output — quote the shortest line that proves the point.** For a long log
|
|
78
|
+
or stack trace, paste the one decisive line and name the file for the rest. A wall of raw log
|
|
79
|
+
buries the finding.
|
|
80
|
+
|
|
81
|
+
**Do not decorate:**
|
|
82
|
+
|
|
83
|
+
- No emoji as decoration.
|
|
84
|
+
- No table when one sentence does the job. Use a table only for real rows and columns.
|
|
85
|
+
- No made-up short forms (cfg, impl, req). The tokenizer splits them the same as the full
|
|
86
|
+
word, so you save nothing and the reader still has to decode.
|
|
87
|
+
|
|
88
|
+
**Write it out in full — normal prose — where being terse causes mistakes:** the numbered
|
|
89
|
+
manual steps above (deploys, SQL, config, restarts), security warnings, and anything hard to
|
|
90
|
+
undo. Clarity wins there, every time.
|
|
91
|
+
|
|
54
92
|
## Check before you send
|
|
55
93
|
|
|
56
94
|
- Can I cut half the words and keep the meaning? Cut them.
|
|
@@ -51,6 +51,9 @@ function reminder() {
|
|
|
51
51
|
' say what it means in plain words instead. Stay exact — keep file names, errors, steps.',
|
|
52
52
|
' 4. Any manual action (deploy, SQL, config, restart) goes in a numbered list under a',
|
|
53
53
|
' "What you need to do:" heading. One action per step, in order.',
|
|
54
|
+
' 5. Trim output: drop filler/pleasantries/hedging, no tool-use narration, quote the',
|
|
55
|
+
' shortest decisive log line (not the whole dump), no decorative tables/emoji. Keep',
|
|
56
|
+
' numbers, negations, code, and errors exact. Clarity always wins over shortness.',
|
|
54
57
|
'',
|
|
55
58
|
'MIRROR THIS PERSON: read how the developer writes to you in this session — the words',
|
|
56
59
|
'and phrases they use, and how long their sentences run — and answer back in that same',
|