# `angular-enterprise` — materialization manifest

When `_init.ps1` selects this preset, it copies the following layout into the spawned project. Files marked `template` undergo placeholder replacement (`__PROJECT_NAME__`, `__PROJECT_SLUG__`, ...).

```
apps/web-angular/
├── angular.json                          template
├── package.json                          template
├── tsconfig.json                         template  (extends @loma-portal/tsconfig/angular.json)
├── eslint.config.js                      template  (extends @loma-portal/eslint-config/angular.js)
├── tailwind.config.js                    template
├── postcss.config.js
├── src/
│   ├── main.ts
│   ├── index.html                        template
│   ├── styles.scss
│   ├── app/
│   │   ├── app.component.ts/.html/.scss
│   │   ├── app.config.ts                  provideHttpClient(withInterceptors(...)) etc.
│   │   ├── app.routes.ts                  lazy-loaded feature routes
│   │   ├── core/
│   │   │   ├── services/                  see preset.json#provides
│   │   │   ├── interceptors/
│   │   │   ├── guards/
│   │   │   ├── models/
│   │   │   ├── utils/
│   │   │   └── constants/
│   │   ├── features/
│   │   │   ├── auth/                      login + refresh flow
│   │   │   └── dashboard/                 stub dashboard
│   │   └── shared/
│   │       └── components/                page-header, section-card, etc.
│   └── assets/
│       └── i18n/
│           ├── en.json
│           └── th.json
└── public/

packages/ui-angular/
├── package.json                          template
├── tsconfig.json                         template  (extends @loma-portal/tsconfig/angular.json)
├── ng-package.json
└── src/
    └── public-api.ts
```

After materialization, `_init.ps1` runs `pnpm install` so the new app is wired into the workspace.

The actual file contents land in Phase 3.
