@intentsolutionsio/vibe-guide 1.0.0 → 1.0.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.
package/README.md CHANGED
@@ -14,6 +14,7 @@ Vibe Guide introduces a completely new way to interact with Claude Code:
14
14
  - **Auto-Summarization**: Hook automatically condenses verbose command output
15
15
 
16
16
  This plugin is perfect for:
17
+
17
18
  - Non-technical founders working with AI to build products
18
19
  - Designers reviewing code changes
19
20
  - Product managers pairing on implementations
@@ -275,6 +276,7 @@ This folder is automatically added to `.gitignore`.
275
276
  ## Troubleshooting
276
277
 
277
278
  ### Plugin not found after install
279
+
278
280
  ```bash
279
281
  # Verify the marketplace is added
280
282
  /plugin marketplace list
@@ -284,6 +286,7 @@ This folder is automatically added to `.gitignore`.
284
286
  ```
285
287
 
286
288
  ### Commands not working
289
+
287
290
  ```bash
288
291
  # Check plugin is installed
289
292
  /plugin list
@@ -294,7 +297,8 @@ This folder is automatically added to `.gitignore`.
294
297
  ```
295
298
 
296
299
  ### Session stuck or corrupted
297
- ```bash
300
+
301
+ ```text
298
302
  # Remove the .vibe folder and start fresh
299
303
  rm -rf .vibe/
300
304
  /vibe-guide:vibe <your goal>
@@ -19,6 +19,7 @@ You are the ONLY user-facing voice. You translate technical work into friendly,
19
19
  ## When to Activate
20
20
 
21
21
  Activate when:
22
+
22
23
  - Worker completes a step and needs results presented
23
24
  - User runs `/vibe-guide:status` to check progress
24
25
  - An error needs to be shown in friendly format
@@ -82,6 +83,7 @@ Do NOT add any other content when there's an error.
82
83
  ## Reading Status
83
84
 
84
85
  Read from `.vibe/status.json`:
86
+
85
87
  - Use `phase` and `step_title` for "Where we are"
86
88
  - Use `what_changed` for "What changed"
87
89
  - Use `what_i_checked` for "What I checked"
@@ -92,6 +94,7 @@ Read from `.vibe/status.json`:
92
94
  ## Success Criteria
93
95
 
94
96
  A successful output:
97
+
95
98
  - Follows the exact format structure
96
99
  - Contains zero technical jargon
97
100
  - Is brief and scannable
@@ -19,6 +19,7 @@ You provide tiny educational nuggets when learning mode is enabled. You explain
19
19
  ## When to Activate
20
20
 
21
21
  Activate when:
22
+
22
23
  - `session.json` has `learning_mode: true`
23
24
  - User runs `/vibe-guide:learn on`
24
25
  - A step has completed and the user wants to learn
@@ -54,6 +55,7 @@ A "route" is an address for different pages. When someone types /about, the rout
54
55
  ## What to Explain
55
56
 
56
57
  Pick from what just happened:
58
+
57
59
  - A file type (.tsx, .json, .css)
58
60
  - An action (import, export, create, edit)
59
61
  - A pattern (component, route, state)
@@ -64,6 +66,7 @@ Choose the concept most useful for a non-technical person to understand.
64
66
  ## Success Criteria
65
67
 
66
68
  A successful explanation:
69
+
67
70
  - Covers exactly one concept
68
71
  - Uses a relatable everyday analogy
69
72
  - Contains no unexplained technical terms
package/agents/worker.md CHANGED
@@ -19,6 +19,7 @@ You execute work in tiny, trackable steps. Each invocation does ONE step only, t
19
19
  ## When to Activate
20
20
 
21
21
  Activate when:
22
+
22
23
  - User runs `/vibe-guide:vibe` to start a session
23
24
  - User runs `/vibe-guide:continue` to execute the next step
24
25
  - A session exists and needs to progress
@@ -86,6 +87,7 @@ Append ONE line to `.vibe/changelog.md`:
86
87
  ## Success Criteria
87
88
 
88
89
  A successful step:
90
+
89
91
  - Completes exactly one atomic action
90
92
  - Updates status.json with accurate information
91
93
  - Uses plain language in all summaries (no technical jargon)
@@ -74,11 +74,13 @@ To turn on, run: /vibe-guide:details on
74
74
  ## Effect
75
75
 
76
76
  When `show_details` is true, the explainer may include:
77
+
77
78
  - File names that changed (not full paths)
78
79
  - Command names that ran (not full output)
79
80
  - Slightly more specific descriptions
80
81
 
81
82
  Still NO:
83
+
82
84
  - Raw diffs
83
85
  - Command output logs
84
86
  - Stack traces
package/commands/guide.md CHANGED
@@ -162,6 +162,7 @@ To fix this:
162
162
  ## Files Created
163
163
 
164
164
  Vibe Guide creates a `.vibe/` folder in your project:
165
+
165
166
  - `session.json` - Your goal and settings
166
167
  - `status.json` - Current progress
167
168
  - `changelog.md` - Log of all steps
package/commands/learn.md CHANGED
@@ -76,6 +76,7 @@ To turn on, run: /vibe-guide:learn on
76
76
  ## Effect
77
77
 
78
78
  When `learning_mode` is true:
79
+
79
80
  - The `vibe-explorer` agent runs after each step
80
81
  - Provides 2-4 sentence explanation of ONE concept
81
82
  - Uses simple analogies, no jargon
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@intentsolutionsio/vibe-guide",
3
- "version": "1.0.0",
3
+ "version": "1.0.2",
4
4
  "description": "Non-technical progress summaries for Claude Code work (hides diffs/log noise).",
5
5
  "keywords": [
6
6
  "ux",