Set up nest-profiler

@eleven-labs/nest-profiler is a Symfony-Web-Profiler-style toolkit for NestJS: every execution gets a token and a /_profiler UI to inspect requests, logs, exceptions, performance spans, and one panel per collector. Wire it into the consumer's app — introspect the project, ask what to add, apply idiomatic wiring, verify it works.

⚠️ Out of production by default — the profiler exposes headers, query params and logs. The default install keeps it in devDependencies, loaded only by a dev entrypoint, so production never installs it. It is the user's call, though: if their production code calls the profiler, or they want it running on an internal / VPN-only environment, install it as a regular dependency behind a ConditionalModule gate and help them harden it (the harden-for-production skill) — don't refuse.

Only adding one collector to an app that already has the core profiler wired? → use the add-nest-profiler-collector skill instead. This skill installs the core (and can add collectors in the same pass).

Workflow

1. Introspect the project first — nothing else until you have this (see below).
2. Choose the install with AskUserQuestion → references/enable-strategies.md: dev dependency + dev entrypoint (recommended, always first) vs dependencies + ConditionalModule (only when production code calls the profiler, or it must run outside local dev).
3. Install and configure the core — ask the config questions that matter (see below).
4. Detect and wire collectors → references/collectors-matrix.md and the family references; multi-select which to add, then ask each collector's key question.
5. Finalize and verify (see below).

Full ProfilerModuleOptions table, storage backends, env vars and headers → references/core-options.md.

Introspect the project