We split this skill into the rules it gives an agent

22 rules. About 0 are common, 13 are distinctive, and 9 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈13

  Distinctive · estimate

  This author's own choices. Worth a look.

• 9

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   When helping with Rails testing:

   line 10
2. Very specific:

   Check existing tests in test/ directory to understand project conventions

   line 13
3. Distinctive:

   Look for test patterns in similar files (models, controllers, etc.)

   line 14
4. Very specific:

   Run all tests: bin/rails test

   line 18
5. Very specific:

   Run specific file: bin/rails test test/models/user_test.rb

   line 19
6. Very specific:

   Run specific test: bin/rails test test/models/user_test.rb:5 (line number)

   line 20
7. Very specific:

   Run with verbose output: bin/rails test -v

   line 21
8. Very specific:

   Use --fail-fast to stop on first failure: bin/rails test --fail-fast

   line 22
9. Distinctive:

   Models: Test business logic, validations, associations

   line 25
10. Distinctive:

    Controllers: Test request/response, status codes, redirects, instance variables

    line 26
11. Distinctive:

    Integration Tests: Test full workflows across multiple components

    line 27
12. Distinctive:

    Fixtures: Use for test data setup

    line 28
13. Very specific:

    Use descriptive test names: test_should_create_valid_user

    line 31
14. Distinctive:

    Test both success and failure cases

    line 32
15. Distinctive:

    Keep tests focused and isolated

    line 33
16. Distinctive:

    Use fixtures for shared test data

    line 34
17. Distinctive:

    Read error messages carefully - they usually point to the issue

    line 38
18. Distinctive:

    Check if test data is set up correctly (fixtures, setup methods)

    line 39
19. Distinctive:

    Verify assertions match the actual behavior

    line 40
20. Very specific:

    Use puts or p to inspect values

    line 41
21. Distinctive:

    Check test isolation - tests shouldn't depend on each other

    line 42
22. Very specific:

    Check test/fixtures/ for test data

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.

• Other versions2 projects use a version of this.

  Word for word · 0

  None found.

  Edited · 0

  None found.

  Wrote their own version · 2

  1. marckohlbrugge/unofficial-37signals-coding-style-guide★ 724same name
  2. mickzijdel/rails-toolkit★ 1same name

  How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

• In this repository5 other files it gives its agents.

  • CLAUDE.mdCLAUDE.md
  • e2e-testingSkill
  • seed-packsSkill
  • theme-creationSkill
  • theme-evaluationSkill