agentleFS
Sign inStart free
loganware05loganware05/captains-compass-cursor/.cursor/skills/node-engineering/SKILL.md

node-engineering

Skill2 starsChanged 31 days agoMITView on GitHub

Implements Node.js services, REST/GraphQL APIs, auth boundaries, validation, and integration tests

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Keep handlers thin; put business logic in clear modules/services.

    line 21
  2. Distinctive:

    Never hard-code secrets; use environment variables / secret managers.

    line 24
  3. Distinctive:

    Add structured logging for failures without leaking sensitive data.

    line 25
  4. Distinctive:

    Add or update integration tests for changed endpoints and failure paths.

    line 26
  5. Very specific:

    Document new env vars in .env.example and PROJECT_CONTEXT.md / TESTING.md.

    line 27
  6. Distinctive:

    Do not weaken auth checks to make tests pass.

    line 35
  7. Very specific:

    Do not commit .env files or credentials.

    line 36
  8. Distinctive:

    Do not expand into unrelated frontend or infrastructure refactors unless the approved plan includes them.

    line 37

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Node.js Engineering

Use this Skill when

Working on Node.js backends, API routes, middleware, background jobs, authentication/authorization, request validation, logging, or server integration tests.

Inputs

  • Approved IMPLEMENTATION_PLAN.md
  • Existing server framework (Express, Fastify, Next.js route handlers, etc.)
  • Auth and environment conventions from PROJECT_CONTEXT.md

Procedure

  1. Match existing project patterns (framework, folder layout, error shape).
  2. Keep handlers thin; put business logic in clear modules/services.
  3. Validate inputs at the boundary; return consistent error responses.
  4. Enforce authentication and authorization on protected routes.
  5. Never hard-code secrets; use environment variables / secret managers.
  6. Add structured logging for failures without leaking sensitive data.
  7. Add or update integration tests for changed endpoints and failure paths.
  8. Document new env vars in .env.example and PROJECT_CONTEXT.md / TESTING.md.

Output

Changed server files, tests, and any env/docs updates reported to the First Mate.

Prohibited actions

  • Do not weaken auth checks to make tests pass.
  • Do not commit .env files or credentials.
  • Do not expand into unrelated frontend or infrastructure refactors unless the approved plan includes them.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free