v1.6.0

Added

• table-driven-testing: New skill for writing table-driven tests outside the JVM — pytest parametrize (Python), Swift Testing @Test(arguments:), Jest/Vitest test.each, Go table-driven subtests, and xUnit [Theory] (C#)
  • Framework mechanics per ecosystem: named cases everywhere (pytest.param(id=...), Go subtest names, Jest interpolated titles), per-framework "regardless of" combination patterns, and the Swift Testing cartesian-product footgun (multiple collections passed to arguments: combine, they don't pair)
  • The same table-design principles as the tabletest skill, applied language-agnostically: decompose concerns into separate parameterised tests, make thresholds visible in the rows, cover every tier and both sides of every boundary, name scenarios by condition (never with the outcome appended), keep expected values literal (no named constants), and give expected-error cases their own test
  • Deliver-don't-ask ambiguity policy: choose the most reasonable interpretation, state it, and deliver complete tests
• Plugin: description and keywords updated to cover the third skill

Changed

• Routing: requests for "table-driven tests" on Java/Kotlin projects now route reliably to the tabletest skill — the new skill's description explicitly defers to it