We split this skill into the rules it gives an agent

31 rules. About 0 are common, 11 are distinctive, and 20 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈11

  Distinctive · estimate

  This author's own choices. Worth a look.

• 20

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Very specific:

   Use a separate test project with naming convention [ProjectName].Tests

   line 12
2. Very specific:

   Create test classes that match the classes being tested (e.g., CalculatorTests for Calculator)

   line 14
3. Very specific:

   Use .NET SDK test commands: dotnet test for running tests

   line 15
4. Distinctive:

   No test class attributes required (unlike MSTest/NUnit)

   line 19
5. Very specific:

   Use fact-based tests with [Fact] attribute for simple tests

   line 20
6. Distinctive:

   Follow the Arrange-Act-Assert (AAA) pattern

   line 21
7. Very specific:

   Use constructor for setup and IDisposable.Dispose() for teardown

   line 23
8. Very specific:

   Use IClassFixture<T> for shared context between tests in a class

   line 24
9. Very specific:

   Use ICollectionFixture<T> for shared context between multiple test classes

   line 25
10. Distinctive:

    Keep tests focused on a single behavior

    line 29
11. Distinctive:

    Avoid testing multiple behaviors in one test method

    line 30
12. Distinctive:

    Use clear assertions that express intent

    line 31
13. Very specific:

    Use [Theory] combined with data source attributes

    line 38
14. Very specific:

    Use [InlineData] for inline test data

    line 39
15. Very specific:

    Use [MemberData] for method-based test data

    line 40
16. Very specific:

    Use [ClassData] for class-based test data

    line 41
17. Very specific:

    Create custom data attributes by implementing DataAttribute

    line 42
18. Distinctive:

    Use meaningful parameter names in data-driven tests

    line 43
19. Very specific:

    Use Assert.Equal for value equality

    line 47
20. Very specific:

    Use Assert.Same for reference equality

    line 48
21. Very specific:

    Use Assert.True/Assert.False for boolean conditions

    line 49
22. Very specific:

    Use Assert.Contains/Assert.DoesNotContain for collections

    line 50
23. Very specific:

    Use Assert.Matches/Assert.DoesNotMatch for regex pattern matching

    line 51
24. Very specific:

    Use Assert.Throws<T> or await Assert.ThrowsAsync<T> to test exceptions

    line 52
25. Distinctive:

    Use fluent assertions library for more readable assertions

    line 53
26. Distinctive:

    Consider using Moq or NSubstitute alongside XUnit

    line 57
27. Distinctive:

    Use interfaces to facilitate mocking

    line 59
28. Distinctive:

    Consider using a DI container for complex test setups

    line 60
29. Very specific:

    Use [Trait("Category", "CategoryName")] for categorization

    line 65
30. Distinctive:

    Use collection fixtures to group tests with shared dependencies

    line 66
31. Very specific:

    Consider output helpers (ITestOutputHelper) for test diagnostics

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.