agentleFS
Hive-AcademyHive-Academy/PtahCode/.claude/skills/nestjs-backend-patterns/SKILL.md

nestjs-backend-patterns

Skill34 starsChanged 10 days agoMITView on GitHub

NestJS backend architecture for multi-tenant SaaS. Use for third-party API providers, Prisma or ZenStack setup, multitenancy, authentication, RBAC or policies, and repositories. Not for retries, events or dynamic modules — use resilient-nestjs-patterns.

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

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Keep authentication, authorization, persistence, and external integration in their respective modules.

    line 13
  2. Very specific:

    Place shared Prisma, auth, and provider adapters under shared/.

    line 14

≈ “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 Backend Architecture Patterns

Apply

  • During a Stage B module task, keep controllers thin and put integration, tenancy, and authorization behind services. Stage A may scaffold only thin primitives.
  • Wrap each external SDK with an injected provider and export a service from its module; keep provider selection and credentials in configuration.
  • Resolve tenant context before database access and deny access when it is missing. Enforce resource permissions at the query or policy boundary, not only in controllers.
  • Keep authentication, authorization, persistence, and external integration in their respective modules.
  • Place shared Prisma, auth, and provider adapters under shared/; place domain controllers and DTOs in the domain's feature-api library.

Load by task

  • For an external API adapter or provider switch, load third-party integration.
  • For tenant isolation and context propagation, load multitenancy.
  • For Prisma or ZenStack setup and access policies, load Prisma and ZenStack.
  • For roles and resource permissions, load authorization.
  • For JWT, Passport, or OAuth, load authentication.

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.