safeword 0.8.0 → 0.8.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "safeword",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "CLI for setting up and managing safeword development environments",
   "type": "module",
   "bin": {
@@ -19,18 +19,6 @@
   "engines": {
     "node": ">=18"
   },
-  "scripts": {
-    "build": "tsup",
-    "dev": "tsup --watch",
-    "test": "vitest run",
-    "test:e2e": "vitest run tests/e2e/",
-    "test:watch": "vitest",
-    "test:coverage": "vitest run --coverage",
-    "typecheck": "tsc --noEmit",
-    "lint": "eslint src tests",
-    "clean": "rm -rf dist",
-    "prepublishOnly": "npm run build && npm test"
-  },
   "dependencies": {
     "commander": "^12.1.0"
   },
@@ -48,5 +36,16 @@
     "claude-code"
   ],
   "author": "",
-  "license": "MIT"
-}
+  "license": "MIT",
+  "scripts": {
+    "build": "tsup",
+    "dev": "tsup --watch",
+    "test": "vitest run",
+    "test:e2e": "vitest run tests/e2e/",
+    "test:watch": "vitest",
+    "test:coverage": "vitest run --coverage",
+    "typecheck": "tsc --noEmit",
+    "lint": "eslint src tests",
+    "clean": "rm -rf dist"
+  }
+}

package/templates/doc-templates/design-doc-template.md

@@ -1,7 +1,7 @@
 # Design: [Feature Name]
 
-**Guide**: `@./.safeword/guides/design-doc-guide.md` - Principles, structure guidelines, and avoiding bloat
-**Template**: `@./.safeword/templates/design-doc-template.md`
+**Guide**: `.safeword/guides/design-doc-guide.md` - Principles, structure guidelines, and avoiding bloat
+**Template**: `.safeword/templates/design-doc-template.md`
 
 **Related**: Feature Spec: `[path]` | Test Definitions: `[path]`
 

package/templates/doc-templates/feature-spec-template.md

@@ -1,7 +1,7 @@
 # Feature Spec: [Feature Name] (Issue #[number])
 
-**Guide**: `@./.safeword/guides/planning-guide.md` - Best practices, INVEST criteria, and examples
-**Template**: `@./.safeword/templates/feature-spec-template.md`
+**Guide**: `.safeword/guides/planning-guide.md` - Best practices, INVEST criteria, and examples
+**Template**: `.safeword/templates/feature-spec-template.md`
 
 **Feature**: [Brief description of the feature]
 

package/templates/doc-templates/task-spec-template.md

@@ -1,7 +1,7 @@
 # Task: [Name]
 
-**Guide**: `@./.safeword/guides/planning-guide.md`
-**Template**: `@./.safeword/templates/task-spec-template.md`
+**Guide**: `.safeword/guides/planning-guide.md`
+**Template**: `.safeword/templates/task-spec-template.md`
 
 ---
 
@@ -148,4 +148,4 @@ The spec takes 30 seconds to write and prevents hours of scope creep.
 | **Task Spec (L1)**    | Bug, improvement, internal, refactor    | Task spec with inline tests          |
 | **Task Spec (L0)**    | Typo, config, trivial                   | Minimal task spec, existing tests    |
 
-For L2 features, use: `@./.safeword/templates/feature-spec-template.md`
+For L2 features, use: `.safeword/templates/feature-spec-template.md`

package/templates/doc-templates/test-definitions-feature.md

@@ -1,7 +1,7 @@
 # Test Definitions: [Feature Name] (Issue #[number])
 
-**Guide**: `@./.safeword/guides/testing-guide.md` - Structure, status tracking, and TDD workflow
-**Template**: `@./.safeword/templates/test-definitions-feature.md`
+**Guide**: `.safeword/guides/testing-guide.md` - Structure, status tracking, and TDD workflow
+**Template**: `.safeword/templates/test-definitions-feature.md`
 
 **Feature**: [Brief description of the feature]
 

package/templates/guides/planning-guide.md

@@ -25,15 +25,15 @@ How to write specs, user stories, and test definitions before implementation.
 
 ## Templates
 
-| Need                            | Template                                             |
-| ------------------------------- | ---------------------------------------------------- |
-| L2 Feature spec                 | `@./.safeword/templates/feature-spec-template.md`    |
-| L1/L0 Task spec                 | `@./.safeword/templates/task-spec-template.md`       |
-| L2 Test definitions             | `@./.safeword/templates/test-definitions-feature.md` |
-| Complex feature design          | `@./.safeword/templates/design-doc-template.md`      |
-| Architectural decision          | `@./.safeword/templates/architecture-template.md`    |
-| Context anchor for complex work | `@./.safeword/templates/ticket-template.md`          |
-| Execution scratch pad           | `@./.safeword/templates/work-log-template.md`        |
+| Need                            | Template                                          |
+| ------------------------------- | ------------------------------------------------- |
+| L2 Feature spec                 | `.safeword/templates/feature-spec-template.md`    |
+| L1/L0 Task spec                 | `.safeword/templates/task-spec-template.md`       |
+| L2 Test definitions             | `.safeword/templates/test-definitions-feature.md` |
+| Complex feature design          | `.safeword/templates/design-doc-template.md`      |
+| Architectural decision          | `.safeword/templates/architecture-template.md`    |
+| Context anchor for complex work | `.safeword/templates/ticket-template.md`          |
+| Execution scratch pad           | `.safeword/templates/work-log-template.md`        |
 
 ---
 
@@ -240,7 +240,7 @@ Test: All existing tests pass, no new mutations
 
 ### How to Fill Out Test Definitions
 
-1. Read `@./.safeword/templates/test-definitions-feature.md`
+1. Read `.safeword/templates/test-definitions-feature.md`
 2. Read user story's Technical Constraints section (if exists)
 3. Fill in feature name, issue number, test file path
 4. Organize tests into logical suites

package/templates/guides/testing-guide.md

@@ -272,7 +272,7 @@ export default defineConfig({
 }
 ```
 
-**Cleanup:** See `@./.safeword/guides/zombie-process-cleanup.md` for killing zombie servers.
+**Cleanup:** See `.safeword/guides/zombie-process-cleanup.md` for killing zombie servers.
 
 ---
 

package/templates/guides/zombie-process-cleanup.md

@@ -202,6 +202,7 @@ ps aux | grep "/Users/alex/projects/my-project"
 | Kill all for this project                | `./scripts/cleanup.sh`                                           |
 | Check what's on port                     | `lsof -i:3000`                                                   |
 | Find zombie processes                    | `ps aux \| grep -E "(node\|playwright\|chromium)"`               |
+| Preview what `pkill -f` would kill       | `pgrep -f "pattern"` (verify before running pkill)               |
 | Kill by process ID                       | `kill -9 <PID>`                                                  |
 
 ---
@@ -210,6 +211,7 @@ ps aux | grep "/Users/alex/projects/my-project"
 
 ❌ **DON'T:** `killall node` (kills all projects)
 ❌ **DON'T:** `pkill -9 node` (kills all projects)
+❌ **DON'T:** `pkill -f "pattern"` without `pgrep -f` first (matches full command line, can kill unintended processes)
 ❌ **DON'T:** Kill processes without checking working directory
 ❌ **DON'T:** Assume zombie browsers will clean themselves up (they won't)
 

package/templates/skills/safeword-tdd-enforcer/SKILL.md

@@ -138,15 +138,37 @@ Before starting Phase 1, create or open a work log:
 - [ ] No hardcoded/mock values
 - [ ] Committed
 
+### Verification Gate
+
+**Before claiming GREEN:** Evidence before claims, always.
+
+```text
+✅ CORRECT                          ❌ WRONG
+─────────────────────────────────   ─────────────────────────────────
+Run: npm test                       "Tests should pass now"
+Output: ✓ 34/34 tests pass          "I'm confident this works"
+Claim: "All tests pass"             "Tests pass" (no output shown)
+```
+
+**The Rule:** If you haven't run the verification command in this response, you cannot claim it passes.
+
+| Claim            | Requires                      | Not Sufficient              |
+| ---------------- | ----------------------------- | --------------------------- |
+| "Tests pass"     | Fresh test output: 0 failures | "should pass", previous run |
+| "Build succeeds" | Build command: exit 0         | "linter passed"             |
+| "Bug fixed"      | Original symptom test passes  | "code changed"              |
+
 **Red Flags → STOP:**
 
-| Flag                | Action                                 |
-| ------------------- | -------------------------------------- |
-| "Just in case" code | Delete it                              |
-| Multiple functions  | Delete extras                          |
-| Refactoring         | Stop - that's Phase 3                  |
-| Test still fails    | Debug (→ systematic-debugger if stuck) |
-| Hardcoded value     | Implement real logic (see below)       |
+| Flag                        | Action                                 |
+| --------------------------- | -------------------------------------- |
+| "should", "probably" claims | Run command, show output first         |
+| "Done!" before verification | Run command, show output first         |
+| "Just in case" code         | Delete it                              |
+| Multiple functions          | Delete extras                          |
+| Refactoring                 | Stop - that's Phase 3                  |
+| Test still fails            | Debug (→ systematic-debugger if stuck) |
+| Hardcoded value             | Implement real logic (see below)       |
 
 ### Anti-Pattern: Mock Implementations