@scotthamilton77/sidekick 0.0.6-alpha → 0.0.8-alpha
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/LICENSE +21 -0
- package/assets/sidekick/reminders/safe-word-liveness.yaml +13 -0
- package/assets/sidekick/reminders/user-prompt-submit.yaml +2 -5
- package/dist/bin.js +17691 -201
- package/dist/daemon.js +31166 -30674
- package/package.json +5 -6
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2025 Scott Hamilton
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
# safe-word-liveness.yaml
|
|
2
|
+
# Liveness probe reminder for plugin detection via safe word response
|
|
3
|
+
id: safe-word-liveness
|
|
4
|
+
blocking: false
|
|
5
|
+
priority: 100 # High priority - inject early
|
|
6
|
+
persistent: false # One-shot per session
|
|
7
|
+
|
|
8
|
+
additionalContext: |
|
|
9
|
+
This session is assisted by Sidekick, an AI coding companion.
|
|
10
|
+
Occasionally you will see additional context injected into the conversation by Sidekick.
|
|
11
|
+
This is important to observe and follow - the user installed this to help you reach quality outcomes.
|
|
12
|
+
|
|
13
|
+
If the user asks whether you know the magic Sidekick word, respond with: {{safeWord}}
|
|
@@ -6,16 +6,13 @@ priority: 10
|
|
|
6
6
|
persistent: true
|
|
7
7
|
|
|
8
8
|
additionalContext: |
|
|
9
|
-
As you answer the user's questions, you can use the following context:
|
|
10
|
-
# claudeMd
|
|
11
|
-
Codebase and user instructions are shown below. Be sure to adhere to these instructions. IMPORTANT: These instructions OVERRIDE any default behavior and you MUST follow them exactly as written.
|
|
12
|
-
|
|
13
9
|
Before proceeding:
|
|
14
10
|
- Verify first (don't tell the user "you're right" based solely on their statements/assertions). Wrong path = 10+ wasted turns. Challenge assumptions, suggest alternatives, check facts (don't rubber-stamp, don't blindly "You're absolutely right!")
|
|
15
11
|
- Review the user's request carefully and ensure you understand the requirements
|
|
16
12
|
- If anything is unclear or ambiguous, ask for clarification rather than making assumptions
|
|
17
|
-
- Track your progress methodically - use
|
|
13
|
+
- Track your progress methodically - use Tasks and update them as you complete steps
|
|
18
14
|
- Stay focused on the immediate task; don't drift into tangential improvements
|
|
15
|
+
- If you identify unrelated issues or new work, give yourself a task to ask the user if they want to tackle them now or add to the user's task tracking system
|
|
19
16
|
- Verify your work before claiming completion (run tests, lint, type-check)
|
|
20
17
|
- Update the user with progress summaries for long-running tasks
|
|
21
18
|
- Use appropriate AGENTS/SKILLS: consider whether there are agents and/or skills that should be leveraged; ask the user if unsure
|