@only1btayy/g2w 1.0.11 → 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.
Files changed (4) hide show
  1. package/README.md +2 -6
  2. package/bin/g2w.js +0 -1
  3. package/package.json +1 -1
  4. package/skills/build2gether.md +1 -1
package/README.md CHANGED
@@ -24,11 +24,7 @@ This is not a workflow system. Not a task runner. This is a protocol for buildin
24
24
  ---
25
25
 
26
26
  ```bash
27
- npm install -g @only1btayy/g2w
28
- ```
29
-
30
- ```
31
- ✅ G2W installed at ~/.claude/ — 9 skills + hooks ready.
27
+ npm install -g @only1btayy/g2w && g2w
32
28
  ```
33
29
 
34
30
  **Works on Mac, Windows, and Linux.**
@@ -145,7 +141,7 @@ Safe git operations — add, commit, push, status, log — run without approval
145
141
  ## How 2 Install
146
142
 
147
143
  ```bash
148
- npm install -g @only1btayy/g2w
144
+ npm install -g @only1btayy/g2w && g2w
149
145
  ```
150
146
 
151
147
  That's it. G2W installs globally into `~/.claude/` automatically — skills and hooks ready in every project, everywhere.
package/bin/g2w.js CHANGED
@@ -12,7 +12,6 @@ if (command === 'install') {
12
12
  } else {
13
13
  process.stdout.write(`${LOGO}
14
14
  Usage:
15
- g2w install — install skills + hooks into ~/.claude/
16
15
  g2w update — update skills to latest version
17
16
  g2w uninstall — remove G2W
18
17
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@only1btayy/g2w",
3
- "version": "1.0.11",
3
+ "version": "1.0.13",
4
4
  "description": "G2W — a relationship protocol for building trust with AI",
5
5
  "bin": {
6
6
  "g2w": "bin/g2w.js"
package/skills/build2gether.md CHANGED
@@ -37,7 +37,7 @@ Once requirements are locked and research is complete:
37
37
  **Planner Agent** writes a complete plan:
38
38
  - No placeholders. Actual code, actual file names, actual decisions.
39
39
  - Declares exactly which files will be created or modified — nothing undeclared
40
- - Writes a concrete definition of done for this specific task
40
+ - Writes a definition of done tied to the user's actual environment — not "it compiled." Specific steps: what build to run, what to open, what to click, what the exact expected result is. If you can't describe how to verify it in the user's setup, the definition of done is not done.
41
41
  - Estimates scope honestly: small / medium / large
42
42
 
43
43
  **Reviewer Agent** does an adversarial pass: