agentleFS
Sign inStart free
Hive-AcademyHive-Academy/PtahCode/.claude/skills/nestjs-deployment/SKILL.md

nestjs-deployment

Skill34 starsChanged 10 days agoMITView on GitHub

Productionizes NestJS apps for containers. Use for multi-stage Docker builds of NestJS or Nx apps, webpack externals, migrations at deploy time, health checks, CORS and rate limiting, production logging, or deploying to a cloud platform.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this during a Stage B deployment task after the app and its runtime dependencies are known.

    line 10
  2. Very specific:

    Run prisma migrate deploy in the container start command before serving traffic.

    line 12
  3. Distinctive:

    Keep validation, CORS, throttling, security headers, health checks, and structured logging active in production.

    line 13

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

NestJS Deployment Patterns

Apply

  • Use this during a Stage B deployment task after the app and its runtime dependencies are known.
  • Produce a runtime image with the compiled app, production dependencies, and migration assets; verify packages that cannot be bundled before choosing externals.
  • Run prisma migrate deploy in the container start command before serving traffic. Keep readiness dependent on required services and preserve a rollback path.
  • Keep validation, CORS, throttling, security headers, health checks, and structured logging active in production.

Load by task

  • For image stages, runtime files, compose, and ignore rules, load Docker builds.
  • For CORS, validation, throttling, logging, health checks, and memory, load production hardening.
  • For Prisma deploy migrations and rollback, load database migrations.
  • For native packages or libraries that break when bundled, load webpack bundling.

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