From 59199def2a5c8ccbfa5493ea95c4b783f15e2ad2 Mon Sep 17 00:00:00 2001 From: Ian White Date: Thu, 5 Mar 2026 18:47:59 -0600 Subject: [PATCH 1/2] fix(tdd): add cross-reference to requirements.mdc Directs agents to read requirements.mdc before authoring given/should strings, ensuring test scenarios are expressed as user-journey-focused functional requirements rather than implementation details or literal values. Closes #127. Made-with: Cursor --- ai/skills/aidd-tdd/SKILL.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ai/skills/aidd-tdd/SKILL.md b/ai/skills/aidd-tdd/SKILL.md index 7e71d2d..3863f73 100644 --- a/ai/skills/aidd-tdd/SKILL.md +++ b/ai/skills/aidd-tdd/SKILL.md @@ -10,6 +10,8 @@ Act as a top-tier software engineer with serious TDD discipline to systematicall ## assert +> Before authoring `given`/`should` strings, read and apply `requirements.mdc` to ensure test scenarios are expressed as functional requirements focused on the user journey, not on implementation details or literal values. + type assert = ({ given: string, should: string, actual: any, expected: any }) { `given` and `should` must clearly state the functional requirements from an acceptance perspective, and should avoid describing literal values. Tests must demonstrate locality: The test should not rely on external state or other tests. From fb9731f4afb888af56843a1ec899ebdccd8dff9c Mon Sep 17 00:00:00 2001 From: Ian White Date: Thu, 5 Mar 2026 18:55:23 -0600 Subject: [PATCH 2/2] fix(tdd): apply review feedback on requirements.mdc reference Replace blockquote callout with a one-line @requirements.mdc constraint inside Constraints {}, matching the established @import pattern used in task-creator.mdc and user-testing.mdc. Made-with: Cursor --- ai/skills/aidd-tdd/SKILL.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/ai/skills/aidd-tdd/SKILL.md b/ai/skills/aidd-tdd/SKILL.md index 3863f73..e932b03 100644 --- a/ai/skills/aidd-tdd/SKILL.md +++ b/ai/skills/aidd-tdd/SKILL.md @@ -10,8 +10,6 @@ Act as a top-tier software engineer with serious TDD discipline to systematicall ## assert -> Before authoring `given`/`should` strings, read and apply `requirements.mdc` to ensure test scenarios are expressed as functional requirements focused on the user journey, not on implementation details or literal values. - type assert = ({ given: string, should: string, actual: any, expected: any }) { `given` and `should` must clearly state the functional requirements from an acceptance perspective, and should avoid describing literal values. Tests must demonstrate locality: The test should not rely on external state or other tests. @@ -73,6 +71,7 @@ For Vitest/Riteway tests: - Never use @testing-library/react (redundant with above patterns) Constraints { + import @requirements.mdc to understand how to express `given`/`should` strings as functional requirements. Unless directed otherwise, always colocate tests with the code they are testing. Carefully think through correct output. Avoid hallucination.