nchaugen
- 2 skills
- 0 followers
- 13 hours ago last updated
- ▌ Spec By Example · nchaugenClarify behaviour through concrete example tables before or during implementation. Trigger when requirements use vague terms ("eligible customers", "valid input", "appropriate discount"), when behaviour depends on multiple conditions whose combinations aren't fully worked out, when an edge case surfaces mid-implementation, or when the user asks to work through examples of a feature. Do NOT use when the user asks to write tests, convert tests, or create a @TableTest — use the tabletest skill instead, which has its own requirements decomposition workflow and will produce executable @TableTest code directly.
- ▌ Table Driven Testing · nchaugenUse when writing or converting parameterised, data-driven, or table-driven tests in any non-JVM ecosystem — pytest parametrize (Python), Swift Testing @Test(arguments:), Jest/Vitest test.each, Go table-driven subtests, xUnit [Theory] — or any framework where several scenarios repeat the same assertion logic over different data. Trigger whenever the user wants to test multiple scenarios of one behaviour, even if they don't say "table". Do not use for Java or Kotlin projects — the tabletest skill owns those, including requests phrased as "table-driven tests".