targeted-file-relevance

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈5

  Distinctive · estimate

  This author's own choices. Worth a look.

• 0

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Use repository metadata and focused search to build a candidate list.

   line 10
2. Distinctive:

   Read primary files first, then expand only when imports, references, or failing checks justify it.

   line 12
3. Distinctive:

   Before editing, state the minimal file set and what would cause expansion.

   line 13
4. Distinctive:

   After editing, confirm no unrelated file was changed.

   line 14
5. Distinctive:

   Do not scan or ingest the whole repository when focused discovery is sufficient.

   line 16

≈ “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.