j-mauro-r/SAT-Dengue-V2 / .agents/skills/deepworkplan/onboard
deepworkplan-onboard
VerifiedMake any repository AI-first — reason (never template) an adapted AGENTS.md, docs/, per-module docs and .agents/ kit from the real repo, discover and verify its full and scoped validation commands and source-to-test mapping, install the DeepWorkPlan skill, and, for a repository onboarded under an earlier version, perform a targeted, non-destructive, idempotent harness upgrade. Use when the developer wants to onboard or upgrade a repository for AI agents.
presets/angular.md
View on GitHub# Preset — Angular (TypeScript)
> Reasoning aid, not a template. Verify against the live repo; detected reality
> wins. Capture the **real** validation command, not the example below.
## Signals that identify this stack
- `angular.json` at the repo root and `@angular/core` in `package.json`
`dependencies` (Angular version → `@angular/*@^N`).
- `src/app/` with components decorated `@Component({ selector, template/
templateUrl, styleUrls })`, and either `@NgModule` declarations
(`app.module.ts`) or **standalone components** (`standalone: true`,
`bootstrapApplication`, `app.config.ts`). **Confirm which the app uses.**
- Services decorated `@Injectable({ providedIn: 'root' })`, RxJS (`rxjs` in
deps, `Observable`/`Subject`/`pipe`), and `@angular/router` for routing.
- `@angular/cli` / `ng` available; `tsconfig.json` plus `tsconfig.app.json` /
`tsconfig.spec.json` splits.
- Package manager from the lockfile: `pnpm-lock.yaml` → pnpm, `yarn.lock` →
yarn, `package-lock.json` → npm. **Infer from the lockfile present.**
- Layout: `src/app/` with feature folders, `components/`, `services/`, `models/`,
`guards/`, `*.module.ts`/`*.routes.ts`; possibly an Nx workspace (`nx.json`,
`project.json`, `libs/`/`apps/`).
## What to look for in recon
- The **real** test runner: Karma + Jasmine (`karma.conf.js`, `*.spec.ts`,
`ng test`) vs Jest (`jest.config.*`, `@angular-builders/jest` or `jest-preset-
angular`, `*.spec.ts`). **Confirm which from the config that exists.**
- The **real** lint gate: `ng lint` backed by `@angular-eslint` (`.eslintrc` /
`eslint.config.js`), and any Prettier step. Capture verbatim.
- The **real** build: `ng build` (and `ng build --configuration production`),
and whether SSR/`@angular/ssr` or `@angular/universal` is in play.
- NgModules vs standalone: drives whether new features need a module entry or a
`providers`/`imports` array on the component/route.
- State management if present: NgRx (`@ngrx/store`, effects, selectors),
signals (`signal()`, `computed()`), or plain services-with-subjects.
## Stack-specific skills/agents/commands to generate
- Skills: `component` (component + template + spec), `service` (injectable +
spec), `module` or `standalone-feature` (depending on the app style),
`guard`/`resolver`, and `ngrx-feature` (store + effects + selectors) if NgRx
is present.
- Agents: baseline + a `component-author` / `frontend-reviewer` persona aware of
change detection (OnPush), the smart-vs-presentational split, and RxJS
subscription/teardown hygiene.
- Commands: the five DWP commands + `code-review`, `pr`, `commit`.
## Doc emphases
- `ARCHITECTURE.md` — module/standalone structure, routing, DI tree, RxJS data
flow, state management (NgRx/signals), HTTP/interceptor layer.
- `STANDARDS.md` — component/service conventions, OnPush change detection,
subscription teardown (`takeUntilDestroyed`/`async` pipe), smart-vs-dumb split.
- `TESTING_GUIDE.md` — Karma/Jasmine vs Jest, `TestBed` setup, `HttpTestingController`,
the real `*.spec.ts` pattern, how to scope one feature's tests.
- Per-module docs: one per feature module / standalone feature (its components,
services, routes, guards).
## Typical validation command (FIND the real one)
Commonly `ng lint && ng test --watch=false --browsers=ChromeHeadless && ng
build`, or wrapped `package.json` scripts (`npm run lint && npm run test:ci &&
npm run build`). **Do not assume** the package manager, the test runner, or the
script names — read `angular.json`, `package.json`, and CI and capture the exact
commands.
## Testing and validation (verified vs example)
The uniform section every preset carries (`README.md` → "The testing section
every preset carries"). Everything below is an **illustrative example until it
is verified against the target repository** in Phase 1 — run the scoped example
on a real path and record the selected/executed count. Items marked *reference
run* were verified once in this skill's contributor environment with the tool
version stated; the target repo's version may differ, so re-verify.
### 1. Full commands
- Tests: `ng test --watch=false` (Karma + Jasmine, `*.spec.ts`) — or `npx jest` when the repo uses `@angular-builders/jest` / `jest-preset-angular`; e2e: Playwright or Cypress (`npx playwright test`, `npx cypress run`).
- Static: `ng lint` (`@angular-eslint`), `npx tsc --noEmit -p tsconfig.app.json` (and `tsconfig.spec.json`), `ng build`.
### 2. Scoped invocation
**Angular CLI + Karma/Jasmine** (documented example — not run in the contributor environment): `ng test --watch=false --include='src/app/orders/**/*.spec.ts'` selects by glob (`--include` accepts globs and file paths); `fdescribe`/`fit` focus a spec at source level (never commit them). **Evidence:** the Karma summary `Executed N of M` — `N` must be the expected count.
**Jest** (flags verified against `jest@29 --help`): `jest <pathPattern>` or `--testPathPattern <regex>` (path filter), `-t "<name>"` (name filter), `--findRelatedTests <src files…>` (impact selection: tests that import the changed sources), `--changedSince <ref>` (impact via git). **Evidence:** the `Tests: N passed` summary. **Zero-selection behavior:** `No tests found` exits **1** by default — `--passWithNoTests` turns that into a silent pass and is forbidden in a gate.
**Playwright** (flags verified against `@playwright/test@1.63 test --help`): `playwright test <file>`, `-g "<title>"`, `--project <name>`, `--only-changed [ref]` (impact via git). `No tests found` is reported when a filter matches nothing — confirm the exit code in the target repo before trusting it in a gate.
### 3. Scoped static checks
- **`ng lint`** runs the workspace's ESLint projects; **`eslint <path>`** (example) scopes natively.
- **`tsc --noEmit -p tsconfig.app.json`** / `ng build`: project-wide. Type-check is **project-wide by design**: `tsc --noEmit` reads `tsconfig.json`; `tsc <file>` ignores the project config and is *not* a sound scoped check. Do not fabricate a per-file variant — a single project-wide run is the real (and usually cheap) option.
### 4. Source-to-test mapping
Co-located `foo.component.spec.ts` / `foo.service.spec.ts` next to each unit; feature-module folders under `src/app/<feature>/`; shared code under `src/app/shared/` and `src/app/core/`.
### 5. Affected consumers
No native impact selector with Karma; with Jest use `--findRelatedTests`. **Blind spots:** `NgModule` provider/import graphs and standalone-component `imports` arrays, `providedIn: 'root'` services (consumed with no module edge), route configs (`app.routes.ts`), `angular.json`, environment files, global styles, `TestBed` fixtures. A change to a `core/` service or an interceptor affects every feature ⇒ full run.
### 6. Escalation and fallback
Shared/core: `src/app/core/` (interceptors, guards, singletons), `src/app/shared/`, `app.config.ts` / root module, route configs. Always full run: `angular.json`, `tsconfig*.json`, `karma.conf.js`/`jest.config.*`, `package.json`/lockfile, ESLint config, `src/environments/*`. **Fallback:** `ng lint && ng test --watch=false && ng build`.
### 7. Layers and posture
Unit (Jasmine/Jest with `TestBed`, `HttpTestingController`) for services, pipes, component logic — fast base; component tests for template behavior; integration where a feature module wires routing + store; a few Playwright/Cypress flows. Unit-first; no ratio quota.
### 8. Zero-selection behavior
Karma reports `Executed 0 of 0` and exits **0** when `--include` matches nothing — a silent empty run: always check the executed count. Jest exits 1 on `No tests found` (unless `--passWithNoTests`).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |