elliot-stack 1.0.12 → 1.0.13
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
|
@@ -11,10 +11,27 @@ The current session ID is: ${CLAUDE_SESSION_ID}
|
|
|
11
11
|
|
|
12
12
|
## Your task
|
|
13
13
|
|
|
14
|
-
Suggest **3 descriptive titles** for this chat session based on the conversation so far. The goal is to make sessions easy to find later.
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
14
|
+
Suggest **3 descriptive titles** for this chat session based on the conversation so far. The goal is to make sessions easy to find later.
|
|
15
|
+
|
|
16
|
+
### Before drafting, do this quick mental pass
|
|
17
|
+
|
|
18
|
+
Ask yourself:
|
|
19
|
+
1. What were the **goals** going in?
|
|
20
|
+
2. What **got built / decided / fixed** that the user might reference later?
|
|
21
|
+
3. What was **noise** — mistakes, abandoned approaches, things they had to redirect you on, dead ends? (These do NOT belong in the title.)
|
|
22
|
+
4. What's **temporary** vs. **lasting**? Temporary states should be mentioned briefly, not led with.
|
|
23
|
+
|
|
24
|
+
Write the title from those answers, NOT from a chronological recap of the chat.
|
|
25
|
+
|
|
26
|
+
### Good titles
|
|
27
|
+
|
|
28
|
+
- Summarize **what was accomplished**, not what was attempted
|
|
29
|
+
- **Title the outputs, not the journey** — exclude mistakes, dead ends, and abandoned approaches. They're not searchable and not useful context for future-you.
|
|
30
|
+
- **Use plain language a future-you would search for.** Avoid jargon like "passthrough," "edge cases," "toggle logic," "auto-cd," "refactored," "overhaul." Say what it does in normal words.
|
|
31
|
+
- **Weight by long-term reference value.** If something will stop mattering in weeks or months (temporary fixes, current-state notes, "until X is available" workarounds), mention it briefly but don't lead with it.
|
|
32
|
+
- List key outputs separated by dashes, commas, or similar (e.g. "Reverse-Engineering /rename, PR #33165 Comment, and Building /better-title Skill")
|
|
33
|
+
- Cover 2-4 main outputs. Resist cramming everything in — first-pass attempts tend to over-include.
|
|
34
|
+
- Are detailed enough that someone skimming a session list can tell exactly what they'd find inside
|
|
18
35
|
- Typically 8-20 words — longer is fine if it adds useful detail
|
|
19
36
|
|
|
20
37
|
## Format
|