@danieljvdm/dev-kit 0.8.0 → 0.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danieljvdm/dev-kit",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "private": false,
   "description": "Declarative project development toolkit with portable agent skills.",
   "license": "MIT",

package/skill-sources.jsonc

@@ -47,5 +47,13 @@
       "include": ["serve-sim"],
       "licensePath": "LICENSE",
     },
+    {
+      "id": "mattpocock-skills",
+      "repository": "https://github.com/mattpocock/skills.git",
+      "ref": "main",
+      "skillsPath": "skills/engineering",
+      "include": ["tdd", "improve-codebase-architecture"],
+      "licensePath": "LICENSE",
+    },
   ],
 }

package/skill-sources.lock.json

@@ -125,6 +125,24 @@
         "serve-sim": "sha256:782f41d4d79100d5bfc9ec1211e5d4766e978299bbb93fd8e34c6f8d2ecf2114"
       },
       "licensePath": "LICENSE"
+    },
+    {
+      "id": "mattpocock-skills",
+      "repository": "https://github.com/mattpocock/skills.git",
+      "ref": "main",
+      "resolved": "2ab958093e83e0ec752e6c1c5932da465bf23e0c",
+      "skillsPath": "skills/engineering",
+      "include": ["tdd", "improve-codebase-architecture"],
+      "skills": ["improve-codebase-architecture", "tdd"],
+      "descriptions": {
+        "improve-codebase-architecture": "Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.",
+        "tdd": "Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests."
+      },
+      "digests": {
+        "improve-codebase-architecture": "sha256:43721b6125a4c703810414e649fbbab252f1f85a62385cdb23f313e0e06ba26a",
+        "tdd": "sha256:ea2d26eda005b10a2de4bdb7de44d33072f2a8e82dbf670952ce30a9c2d7c475"
+      },
+      "licensePath": "LICENSE"
     }
   ]
 }

package/skills/testing/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: testing
+description: Set an extremely high bar for automated tests. Use whenever software work raises the question of adding, changing, retaining, or removing tests.
+---
+
+# Testing
+
+**If in doubt, don't test it.**
+
+Committed tests must prove durable value. Tests are permanent product code, not a reflexive companion to each source file.
+
+Write a test only when every condition holds:
+
+- It protects stable product behavior rather than an implementation detail.
+- A regression is plausible and would be costly.
+- The behavior is observable through a stable public seam.
+- The test will survive likely refactors.
+- The expected result is independent of the implementation.
+- Existing tests, types, static checks, or a smoke check cannot cover the risk adequately.
+
+If any condition fails, skip the test and use the cheapest sufficient verification instead. Moving MVP behavior often warrants no committed tests.
+
+Test capabilities, not files. Use the fewest tests that protect the risk, and ignore coverage targets unless the user explicitly asks for them.

package/skills/testing/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Testing"
+  short_description: "Set a very high bar for automated tests"
+  default_prompt: "Use $testing to decide whether this change truly warrants any automated tests."