@nolrm/contextkit 0.15.0 → 0.15.1

package/README.md

@@ -90,7 +90,7 @@ Each platform generates bridge files that the AI tool auto-reads. If a bridge fi
 
 - Reads `glossary.md` → `checkout` = checkout process; `customer` = customer account
 - Applies `code-style.md` → strict TS, functional components
-- Follows `testing.md` → numbered test cases
+- Follows `testing.md` → testing levels, change-driven test selection, numbered test cases
 
 **Result (diff)**
 
@@ -161,7 +161,7 @@ ContextKit installs reusable slash commands for supported platforms:
 | `/squad`               | Kick off a squad task — one task or many (auto-detects batch mode). Pushes back with clarifying questions if the task is vague. |
 | `/squad-architect`     | Design the technical plan from the PO spec                                                                                      |
 | `/squad-dev`           | Implement code following the architect plan                                                                                     |
-| `/squad-test`          | Write and run tests against acceptance criteria                                                                                 |
+| `/squad-test`          | Classify test levels, write and run tests against acceptance criteria                                                           |
 | `/squad-review`        | Review the full pipeline and give a verdict                                                                                     |
 | `/squad-doc`           | Create companion `.md` files for new/modified code after review passes                                                          |
 | `/squad-auto`          | Auto-run the full pipeline after kickoff (recommended, sequential)                                                              |

package/lib/commands/install.js

@@ -451,6 +451,38 @@ Your testing standards will be automatically generated based on your existing te
 
 Run \`/analyze\` to generate this content.
 
+## Testing Levels
+
+Follow the **Testing Trophy** philosophy: integration tests are the sweet spot — they give the most confidence per test written. Unit tests cover isolated logic. E2E covers critical user paths only.
+
+> Default bias: when in doubt, write an integration test, not a unit test.
+
+### The Three Levels
+
+| Level | What it tests | Typical tools |
+|-------|--------------|--------------|
+| **Unit** | A single function, class, or component in isolation — dependencies mocked | Jest, testing-library (component only) |
+| **Integration / Page** | A full page or feature rendered with its real component tree — only external APIs/services mocked | Jest + testing-library, Supertest |
+| **E2E** | A complete user flow in a real browser or process | Playwright, Cypress |
+
+### Change-Driven Decision Table
+
+Before writing any tests, classify what changed and apply the required level(s):
+
+| What changed | Unit | Integration / Page | E2E |
+|---|:---:|:---:|:---:|
+| Pure function or utility | ✅ | — | — |
+| New CLI command or module | ✅ | ✅ (cross-command) | — |
+| UI component (used in 1 place) | ✅ | — | — |
+| UI component (used in 2+ contexts: edit/view/create/…) | ✅ | ✅ one per context | — |
+| New page or route | — | ✅ | — |
+| Multi-step user flow | — | — | ✅ |
+| Bug fix | At the level the bug was visible | | |
+
+### Context Coverage Rule
+
+If a component is rendered in **two or more contexts** (e.g. Edit page, View page, Create page), each context requires its own integration test. A single unit test is not sufficient — it cannot catch wiring bugs that only appear in context.
+
 ## ⭐ REQUIRED: Numbered Test Cases
 
 **All test cases MUST use numbered descriptions for easy tracking and debugging:**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nolrm/contextkit",
-  "version": "0.15.0",
+  "version": "0.15.1",
   "description": "ContextKit - Context Engineering for AI Development. Provide rich context to AI through structured MD files with standards, code guides, and documentation. Works with Cursor, Claude, Aider, VS Code Copilot, and more.",
   "main": "lib/index.js",
   "bin": {