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

Author: ianwhitedeveloper

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.