Profile scope and official documentation

Read docs/agents/stack.md when present. Apply this custom stack only to apps selecting the default NestJS profile or explicitly adopting it. In existing apps with another stack preserve conventions; this skill does not authorize migration. For new unconfigured apps agree on the profile using setup-mvskills.

For API/CLI facts start with https://docs.nestjs.com/llms.txt and fetch relevant linked official pages. Use https://docs.nestjs.com/llms-full.txt as a fallback, searching relevant sections rather than loading it wholesale. Match docs to installed versions and command --help; the selected profile owns architecture choices.

Driving the NestJS CLI

The CLI keeps boilerplate, naming and module registration consistent, so use it for every artefact it knows how to generate. Hand-write only what it can't produce (use cases, ports, adapters, DTOs — see the nestjs-feature skill templates). Where files go is defined by the nestjs-architecture skill; this skill is about how to run the commands. Before generating or scaffolding, invoke nestjs-architecture through the host's skill mechanism, or read its installed entrypoint if the skill tool is unavailable.

Ground rules