20.17Test-generator skill

Do not prompt:

“Write tests.”

Use:

Generate tests from the approved business rules and API contract.

For each requirement, consider:

1. happy path
2. negative validation
3. boundary values
4. omitted optional fields
5. explicit nulls
6. duplicate/replay
7. concurrent duplicate requests
8. downstream failure
9. partial failure
10. relationship correctness
11. authorization/permission behavior
12. eventual-consistency behavior where applicable

Classify each test as:
MUnit
integration
end-to-end
performance
manual/exploratory

Do not create redundant E2E tests when a lower test layer
proves the behavior more reliably.

This last sentence prevents enormous brittle suites.