We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈2

  Distinctive · estimate

  This author's own choices. Worth a look.

• 4

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   When writing Node.js backend logic, prioritize non-blocking IO and robust error handling:

   line 11
2. Very specific:

   Event Loop: Never write synchronous, CPU-intensive code (JSON.parse on massive objects, sync file reads) in the main request path.

   line 13
3. Very specific:

   Async/Await: Use async/await over raw Promises or callbacks.

   line 14
4. Distinctive:

   Error Handling: Do not swallow errors. Handle uncaught exceptions and unhandled promise rejections gracefully, logging them and exiting if …

   line 15
5. Distinctive:

   Streams: When dealing with large files or network responses, use Streams instead of buffering the entire payload into memory.

   line 16
6. Very specific:

   Security: Avoid eval(), sanitize inputs before passing them to exec() or spawn(), and never expose raw stack traces to the client.

   line 17

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