# `presets/stacks/`

Stack presets scaffold the technical foundation of a spawned project — frontend framework, backend runtime, ORM, auth strategy. Each preset declares which apps and packages it materializes when listed in `project.config.json#extends`.

| Preset               | Status | Materializes (after Phase 3/4)                                             |
| -------------------- | ------ | -------------------------------------------------------------------------- |
| `angular-enterprise` | stable | `apps/web-angular/`, Angular base config, Transloco i18n, Material setup   |
| `nextjs-enterprise`  | stable | `apps/web-next/`, App Router scaffold, next-intl, shadcn/ui baseline       |
| `nestjs-enterprise`  | stable | `apps/api-nest/`, AuthModule, RbacModule, AuditModule, BullMQ              |
| `dotnet-enterprise`  | stable | `dotnet/src/{Api,Application,Domain,Infrastructure,Shared}/`, MediatR + EF |

Each preset folder contains:

- `preset.json` — manifest validated against [`../preset.schema.json`](../preset.schema.json)
- `README.md` — what the preset does and how it composes with others
- `manifest.md` — human-readable list of files materialized

The actual app code is **not** stored here. Presets reference the foundation generated in Phases 3 and 4 — they are recipes, not source. This keeps presets versionable without duplicating thousands of lines of scaffold code.
