pawmode 1.4.0 → 1.5.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.
package/package.json
CHANGED
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: c-lockin
|
|
3
|
+
description: Lock In Mode — orchestrate distraction blocking, environment setup, and session tracking.
|
|
4
|
+
tags: [lockin, focus, productivity, deep-work, pomodoro, distraction-blocking]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Behavior
|
|
8
|
+
|
|
9
|
+
You run lock-in sessions using generated shell scripts — fast, one command.
|
|
10
|
+
Be FAST. Say one short line like "Locking you in for 90 min" then run TWO commands max. Don't narrate steps. Only speak again when done ("Locked in until HH:MM") or if something fails.
|
|
11
|
+
|
|
12
|
+
## Starting a Session
|
|
13
|
+
|
|
14
|
+
When the user says "lock in", "focus", "deep work", etc:
|
|
15
|
+
|
|
16
|
+
1. Read `~/.config/openpaw/lockin.json`. If missing → suggest `openpaw lockin setup`
|
|
17
|
+
2. Check `~/.config/openpaw/lockin-session.json` — if `endsAt` is in the future, session is already active. Tell the user.
|
|
18
|
+
3. If config has `askEachTime` sites or apps, ask the user briefly which to include this session
|
|
19
|
+
4. Calculate `endsAt` = now + duration minutes (ISO 8601 format, e.g. `2026-03-03T16:30:00.000Z`)
|
|
20
|
+
5. Say ONE short line like "Locking you in for 90 min"
|
|
21
|
+
6. Generate scripts + run:
|
|
22
|
+
|
|
23
|
+
```bash
|
|
24
|
+
openpaw lockin gen-scripts --ends "ENDS_AT_ISO8601" --extra-sites "site1,site2" --extra-apps "App1,App2"
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
Omit `--extra-sites` and `--extra-apps` if none were chosen from askEachTime.
|
|
28
|
+
|
|
29
|
+
Then immediately run:
|
|
30
|
+
|
|
31
|
+
```bash
|
|
32
|
+
bash /tmp/lockin-start.sh
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
7. Say "Locked in until HH:MM"
|
|
36
|
+
|
|
37
|
+
That's it — TWO bash commands to start a session.
|
|
38
|
+
|
|
39
|
+
## Ending a Session
|
|
40
|
+
|
|
41
|
+
When the user says "stop", "end session", "I'm done":
|
|
42
|
+
|
|
43
|
+
1. Read `~/.config/openpaw/lockin-session.json` to get session data
|
|
44
|
+
2. Run:
|
|
45
|
+
|
|
46
|
+
```bash
|
|
47
|
+
bash /tmp/lockin-end.sh
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
3. Read the output for git stats
|
|
51
|
+
4. If `obsidianLog` is true in config: `obsidian-cli append daily "## Lock In Session\n- Duration: X min\n- Commits: N\n..."`
|
|
52
|
+
5. Give a brief warm summary: duration, commits + messages, lines changed, encouraging note referencing SOUL.md personality
|
|
53
|
+
|
|
54
|
+
## Reconfigure
|
|
55
|
+
|
|
56
|
+
```bash
|
|
57
|
+
openpaw lockin setup
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
## Guidelines
|
|
61
|
+
|
|
62
|
+
- Be FAST — one line to start, two commands, one line when done
|
|
63
|
+
- Never explain or narrate each step — just do it
|
|
64
|
+
- If something fails, mention it briefly and move on
|
|
65
|
+
- Only start when the user explicitly asks
|
|
66
|
+
- Reference SOUL.md for personality in summaries
|