codebyplan 1.13.3 → 1.13.5

package/templates/skills/cbp-setup-eslint/reference/base.md

@@ -1,82 +1,71 @@
-# base — TypeScript foundation (ESLint v10 flat config)
+# base — TypeScript (official typescript-eslint setup)
 
-The foundation every TypeScript app shares: ESLint flat config, type-checked
-`typescript-eslint` rules, security scanning, and Prettier. Maps to the CBP **`base`** DB
-preset (`tech_match.requires: ["TypeScript"]`).
+> **Official source**: https://typescript-eslint.io/getting-started/ (+ typed-linting). Verified
+> 2026-05-31. ESLint flat config (`eslint.config.mjs`). This is the typescript-eslint quickstart
+> verbatim — no additions.
 
-> **Verified 2026-05-31.** ESLint is on **v10** — flat config (`eslint.config.mjs`) is the
-> only native format (legacy `.eslintrc*` was removed). `defineConfig` from `eslint/config`
-> is the canonical wrapper for every stack below.
+The foundation for any TypeScript project.
 
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `eslint` | `10.4.1` | the linter (flat config only) |
-| `@eslint/js` | `10.0.1` | `js.configs.recommended` |
-| `typescript-eslint` | `8.60.0` | unified parser + plugin + presets |
-| `eslint-config-prettier` | `10.x` | turns off formatting rules (subpath `/flat`) |
-| `eslint-plugin-security` | `^3` | OWASP-style heuristics |
-| `eslint-plugin-no-secrets` | `^2.1` | high-entropy string detection |
-| `globals` | `17.6.0` | env global definitions |
+## Install
 
 ```bash
-pnpm add -D eslint @eslint/js typescript-eslint eslint-config-prettier \
-  eslint-plugin-security eslint-plugin-no-secrets globals
+npm install --save-dev eslint @eslint/js typescript typescript-eslint
 ```
 
-## Flat config
+## eslint.config.mjs — quickstart (no type info)
 
 ```js
-// eslint.config.mjs
+// @ts-check
+import js from "@eslint/js";
 import { defineConfig } from "eslint/config";
+import tseslint from "typescript-eslint";
+
+export default defineConfig(
+  js.configs.recommended,
+  tseslint.configs.recommended,
+);
+```
+
+## eslint.config.mjs — typed linting (recommended by typescript-eslint)
+
+```js
 import js from "@eslint/js";
+import { defineConfig } from "eslint/config";
 import tseslint from "typescript-eslint";
-import security from "eslint-plugin-security";
-import noSecrets from "eslint-plugin-no-secrets";
-import prettier from "eslint-config-prettier/flat";
 
-export default defineConfig([
+export default defineConfig(
   js.configs.recommended,
-  ...tseslint.configs.recommendedTypeChecked, // type-aware: no-floating-promises, etc.
-  security.configs.recommended,
-  { plugins: { "no-secrets": noSecrets }, rules: { "no-secrets/no-secrets": ["warn", { tolerance: 4.5 }] } },
+  tseslint.configs.recommended,
+  tseslint.configs.recommendedTypeChecked,
   {
     languageOptions: {
       parserOptions: {
-        projectService: true,                 // current type-info mechanism
-        tsconfigRootDir: import.meta.dirname,
+        projectService: true,
       },
     },
   },
-  { rules: { "security/detect-object-injection": "off" } }, // famously noisy
-  prettier, // MUST be last
-]);
+);
 ```
 
-## Gotchas
+## Run
 
-- **`recommended` vs `recommendedTypeChecked`.** The type-checked preset is what enables the
-  genuinely valuable rules (`no-floating-promises`, `no-misused-promises`, `no-unsafe-*`) but
-  needs type info and is **much slower** — scope it to `**/*.ts`/`**/*.tsx` and disable on JS
-  config files with `tseslint.configs.disableTypeChecked`.
-- **`projectService: true`** replaces the old `project: "./tsconfig.json"`. It auto-finds the
-  nearest `tsconfig.json` per file and lints out-of-project files (like `eslint.config.mjs`)
-  without a `tsconfig.eslint.json`. Always pair it with `tsconfigRootDir: import.meta.dirname`.
-- **`tseslint.config()` is deprecated** in favour of core `defineConfig` from `eslint/config`
-  (a near-exact clone). The `tseslint.configs.*` presets are unchanged.
-- **Prettier last.** `eslint-config-prettier/flat` must come after every rule-defining config
-  so it can switch off conflicting stylistic rules.
+```bash
+npx eslint .
+```
 
-## CBP preset divergence
+## Notes (from the official docs)
 
-CBP's `base` DB preset currently pins `eslint: ^9.0.0` / `typescript-eslint: ^8.0.0` and
-keeps several `@typescript-eslint/no-unsafe-*` rules at `warn`. The setup above reflects the
-**latest** (`eslint@10`); both are flat-config and interoperate. Bumping the preset to v10 is
-out of scope for the skill (no DB/preset changes) — adopt v10 per-repo when you regenerate.
+- The base recommended config is `js.configs.recommended` (from `@eslint/js`, imported as `js`) —
+  **not** `eslint.configs.recommended`. `defineConfig` is imported from `eslint/config`.
+- `tseslint.configs.recommendedTypeChecked` adds rules that **require type information**; enable it
+  with `parserOptions.projectService: true`.
+- typescript-eslint *"strongly recommend[s] you do use type-aware linting,"* while noting it incurs a
+  performance penalty (TypeScript builds the project before ESLint lints).
+- `// @ts-check` type-checks the config file itself (optional). Use `eslint.config.js` if
+  `package.json` has `"type": "module"`.
+- Stricter presets are available: `strict` / `strictTypeChecked`, `stylistic` / `stylisticTypeChecked`.
 
-## Official docs
+## Source
 
-- Configuration files: https://eslint.org/docs/latest/use/configure/configuration-files
-- Typed linting: https://typescript-eslint.io/getting-started/typed-linting/
-- `projectService`: https://typescript-eslint.io/blog/project-service/
+- https://typescript-eslint.io/getting-started/
+- https://typescript-eslint.io/getting-started/typed-linting/

package/templates/skills/cbp-setup-eslint/reference/cli.md

@@ -1,56 +1,63 @@
-# cli — Node CLI tool overrides
+# cli — Node CLI tool (convention — no official preset)
 
-For Node CLI packages with a `bin` (the CBP `codebyplan` package). Layers a small **override
-block** on top of [base](base.md) + [node](node.md). Maps to the CBP **`cli`** DB preset
-(`tech_match.requires_capabilities: ["cli-bin"]`).
+> **There is no official "CLI" ESLint config or preset.** Neither ESLint nor Node publishes one. A
+> "CLI config" is a convention: a scoped `files` override inside your normal flat config that relaxes
+> a few rules a CLI legitimately trips. Only the individual official rule/plugin docs below are
+> authoritative (verified 2026-05-31).
 
-> **Verified 2026-05-31.** There is no "CLI" ESLint plugin — the convention is a scoped
-> rule-override block.
+## What a CLI override does
 
-## What it does
-
-A CLI legitimately (a) talks to the user via `console`, and (b) operates on user-supplied
-filesystem paths and dynamic keys — so the `eslint-plugin-security` heuristics that flag those
-produce noise, not findings. Relax them, **scoped narrowly** to the CLI surface.
-
-## Flat config (override block)
+A CLI prints to stdout/stderr and operates on user-supplied paths, so two official rules are commonly
+relaxed **scoped to the CLI source**:
 
 ```js
-// eslint.config.mjs — appended after base + node + security configs
+// eslint.config.mjs — appended after your base config
 export default [
-  // ...base, node, security.configs.recommended, etc.
+  // ...your base config (e.g. typescript-eslint, see base.md)...
   {
-    files: ["bin/**/*.{js,ts,mjs}", "src/cli/**/*.{js,ts}"],
+    files: ["bin/**", "src/cli/**"],
     rules: {
-      "no-console": "off", // console output IS the CLI's UI
-
-      // CLIs operate on user paths and dynamic keys by design:
+      "no-console": "off",
+      // only if eslint-plugin-security is installed (see below):
       "security/detect-non-literal-fs-filename": "off",
       "security/detect-object-injection": "off",
-
-      // optional, if eslint-plugin-n is in use (CLIs call process.exit):
-      // "n/no-process-exit": "off",
     },
   },
 ];
 ```
 
-## Gotchas
+## Official sources for the individual rules
+
+### `no-console` (core ESLint rule)
+Disallows `console` calls (treated as debugging output). It is **off** in `eslint:recommended`, so you
+only need to turn it `off` if your base config enabled it. The rule page shows the inline form, e.g.:
+
+```js
+/* eslint no-console: ["error", { allow: ["warn", "error"] }] */
+```
+
+Source: https://eslint.org/docs/latest/rules/no-console
 
-- **Scope via `files`** — do NOT disable these repo-wide; the same rules are valuable in
-  server/library code.
-- The two `security/*` lines require `eslint-plugin-security` to be installed and registered
-  (otherwise ESLint errors "rule not found"). If the project has no security plugin, only the
-  `no-console: "off"` line applies.
+### `eslint-plugin-security` (official community plugin)
+The `security/*` rules above exist only if this plugin is installed and registered:
+
+```bash
+npm install --save-dev eslint-plugin-security
+```
+
+```js
+const pluginSecurity = require('eslint-plugin-security');
+module.exports = [pluginSecurity.configs.recommended];
+```
 
-## CBP preset divergence
+Its README notes the plugin *"finds a lot of false positives which need triage by a human"* — which is
+why CLIs relax `detect-non-literal-fs-filename` / `detect-object-injection` on user-path code.
 
-The CBP `cli` preset matches the rule set above exactly (`no-console`,
-`security/detect-non-literal-fs-filename`, `security/detect-object-injection` all off) and is
-capability-gated on `cli-bin`. The repo's own `packages/codebyplan-package/eslint.config.mjs`
-already applies this. No divergence — this doc just documents the convention.
+Source: https://github.com/eslint-community/eslint-plugin-security
 
-## Official docs
+## Notes
 
-- Convention (no upstream doc); rules: https://eslint.org/docs/latest/rules/no-console and
-  https://github.com/eslint-community/eslint-plugin-security
+- Keep the relaxations **narrowly scoped via `files`** — do not disable these repo-wide.
+- If your project does not use `eslint-plugin-security`, only the `no-console: "off"` line applies.
+- The ESLint `no-console` page does **not** ship a full standalone `eslint.config.mjs` example — only
+  the inline-comment and `rules`-object forms shown above.

package/templates/skills/cbp-setup-eslint/reference/e2e.md

@@ -1,68 +1,78 @@
-# e2e — Playwright / WebdriverIO / Mocha test rules
+# e2e — Playwright / WebdriverIO / Mocha (official setups)
 
-For end-to-end specs. Three runners appear across CBP repos: **Playwright** (web), **WebdriverIO**
-(Tauri desktop), and **Mocha** (the framework WDIO drives). Each is a **directory-scoped**
-override. Playwright maps to the CBP **`testing-e2e`** preset
-(`tech_match.requires: ["Playwright"]`); WebdriverIO + Mocha are **gap stacks — no preset**.
+> **Official sources** (verified 2026-05-31):
+> - Playwright — https://github.com/mskelton/eslint-plugin-playwright
+> - WebdriverIO — https://github.com/webdriverio/webdriverio/tree/main/packages/eslint-plugin-wdio
+> - Mocha — https://github.com/lo1tuma/eslint-plugin-mocha
 
-> **Verified 2026-05-31.** Version traps: Playwright is **2.10.4** (not the 0.15.x search
-> sometimes returns); Mocha 11.x uses **`configs.recommended`** — NOT `configs.flat.recommended`.
+Each E2E runner has its own official plugin. Use the one(s) matching your test runner.
 
-## Packages
-
-| Package | Latest | Flat key |
-| ------- | ------ | -------- |
-| `eslint-plugin-playwright` | `2.10.4` | `configs['flat/recommended']` |
-| `eslint-plugin-wdio` | `9.27.2` | `configs['flat/recommended']` |
-| `eslint-plugin-mocha` | `11.3.0` | `configs.recommended` (NOT `.flat`) |
+## Playwright
 
 ```bash
-pnpm add -D eslint-plugin-playwright   # web
-pnpm add -D eslint-plugin-wdio eslint-plugin-mocha   # Tauri / WebdriverIO desktop
+npm install -D eslint-plugin-playwright
 ```
 
-## Flat config
-
 ```js
-// eslint.config.mjs
+import { defineConfig } from "@eslint/config";
 import playwright from "eslint-plugin-playwright";
-// desktop: import { configs as wdioConfigs } from "eslint-plugin-wdio";
-// desktop: import mocha from "eslint-plugin-mocha";
 
-export default [
-  // Playwright — scope to the web e2e dir
+export default defineConfig([
   {
-    ...playwright.configs["flat/recommended"],
-    files: ["e2e/**", "**/*.e2e.{ts,js}"],
-    rules: { ...playwright.configs["flat/recommended"].rules, "no-console": "off" },
+    files: ["tests/**"],
+    extends: [playwright.configs["flat/recommended"]],
+    rules: {
+      // Customize Playwright rules
+    },
   },
+]);
+```
+
+Key: **`playwright.configs["flat/recommended"]`**. The README notes you may need to change `files` to
+match your Playwright test patterns.
+
+## WebdriverIO
+
+```bash
+npm install eslint-plugin-wdio --save-dev
+```
+
+```js
+// eslint.config.mjs
+import { configs as wdioConfig } from "eslint-plugin-wdio";
 
-  // WebdriverIO + Mocha (Tauri desktop) — scope to the wdio spec dir
-  // { ...wdioConfigs["flat/recommended"], files: ["test/**", "e2e/**"] },
-  // { ...mocha.configs.recommended, files: ["test/**/*.{ts,js}"] },
+export default [
+  wdioConfig["flat/recommended"],
 ];
 ```
 
-## Gotchas
+Key: **`configs["flat/recommended"]`**. Requires ESLint v9 + flat config.
+
+## Mocha
+
+```bash
+npm install --save-dev eslint-plugin-mocha
+```
+
+```js
+import mochaPlugin from "eslint-plugin-mocha";
+
+export default [
+  mochaPlugin.configs.recommended, // or `mochaPlugin.configs.all`
+];
+```
 
-- **Scope every e2e override via `files`** — Playwright/WDIO/Mocha rules false-positive on
-  unit tests, and Testing-Library rules false-positive on e2e specs.
-- **Mocha 11.x = `mocha.configs.recommended`** — `mocha.configs.flat.recommended` is
-  `undefined` in 11.x (it only exists on the unreleased 12.x main branch) and crashes config
-  load. Don't copy a `.flat.recommended` example.
-- **WebdriverIO**: `eslint-plugin-wdio@9` requires ESLint 9+; when `typescript-eslint` is
-  present its recommended config auto-swaps `wdio/await-expect` → `wdio/no-floating-promise`.
-- The CBP web app keeps Playwright specs in `e2e/**` with a Vitest sibling override for
-  `e2e/**/__tests__/**` — mirror that split if you co-locate unit tests under `e2e/`.
+Key (latest published v11.x): **`mochaPlugin.configs.recommended`** — **NOT** `configs.flat.recommended`
+and **NOT** `configs["flat/recommended"]`. Plain dot-notation, no `flat` segment. Scope to your spec
+files via a `{ files: [...], ...mochaPlugin.configs.recommended }` wrapper if needed.
 
-## CBP preset divergence
+## Notes (from the official docs)
 
-CBP's `testing-e2e` preset covers **Playwright only** (`eslint-plugin-playwright: ^2.0.0`,
-`no-console: off`). There is **no** preset for WebdriverIO or Mocha — the Tauri desktop e2e
-config is manual. The skill does not add presets for the gap runners.
+- Scope each runner's config to its test directory via `files` so the rules don't bleed onto other
+  files.
+- **No `flat/` prefix** on the key: Mocha (`configs.recommended`). **Bracketed `flat/` key**:
+  Playwright, WebdriverIO. Mocha's README is flat-config only (no legacy `.eslintrc` shown).
 
-## Official docs
+## Source
 
-- Playwright: https://github.com/mskelton/eslint-plugin-playwright
-- WebdriverIO: https://github.com/webdriverio/webdriverio/tree/main/packages/eslint-plugin-wdio
-- Mocha: https://github.com/lo1tuma/eslint-plugin-mocha
+See the three URLs above.

package/templates/skills/cbp-setup-eslint/reference/jest.md

@@ -1,59 +1,43 @@
-# jest — Jest test-file rules
+# jest — Jest test files (official eslint-plugin-jest setup)
 
-For apps that test with Jest (CBP `apps/backend` NestJS specs, `livebyplan` Expo). **Gap
-stack — no CBP DB preset** (the `testing` preset is Vitest-only). Layers a test-scoped
-override on top of [base](base.md).
+> **Official source**: https://github.com/jest-community/eslint-plugin-jest (verified 2026-05-31). This
+> is the plugin's official flat-config usage.
 
-> **Verified 2026-05-31.** `eslint-plugin-jest` uses the **bracketed** flat-config keys
-> `configs['flat/recommended']` / `['flat/style']` (the un-prefixed keys are legacy eslintrc).
-
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `eslint-plugin-jest` | `29.15.2` | Jest rules |
+## Install
 
 ```bash
-pnpm add -D eslint-plugin-jest
+npm install --save-dev eslint eslint-plugin-jest
 ```
 
-Peers: `eslint ^8.57 || ^9 || ^10`, `@typescript-eslint/eslint-plugin ^8`, `jest`.
-
-## Flat config
+## eslint.config.mjs — recommended config
 
 ```js
-// eslint.config.mjs
 import jest from "eslint-plugin-jest";
 
 export default [
   {
-    files: ["**/*.{test,spec}.{ts,tsx,js,jsx}", "**/__tests__/**/*.{ts,tsx,js,jsx}"],
+    // update this to match your test files
+    files: ["**/*.spec.js", "**/*.test.js"],
     ...jest.configs["flat/recommended"],
-    rules: {
-      ...jest.configs["flat/recommended"].rules,
-      ...jest.configs["flat/style"].rules, // optional stylistic rules
-      // type-aware: hand the unbound-method check to the jest-aware version
-      "@typescript-eslint/unbound-method": "off",
-      "jest/unbound-method": "error",
-    },
   },
 ];
 ```
 
-## Gotchas
-
-- Keys are **`configs['flat/recommended']`** / **`['flat/style']`** (bracketed) — the
-  unprefixed `configs.recommended` is the legacy eslintrc preset.
-- **`jest/unbound-method`** extends `@typescript-eslint/unbound-method`; turn the base rule
-  off on test files and enable the jest version (needs `@typescript-eslint/parser` + type
-  info). Type-aware jest rules safely no-op when type info is absent.
-- Avoid pinning `flat/all` long-term — it enables every rule and can break on minor releases.
+The README's manual-rules example registers globals explicitly:
+`languageOptions: { globals: jest.environments.globals.globals }`.
 
-## CBP preset divergence
+## Notes (from the official docs)
 
-There is **no** CBP `testing-jest` preset. NestJS/Expo Jest specs are currently linted only by
-the base rules. Add the override above per-repo; the skill does not add a preset.
+- Config keys: **`jest.configs["flat/recommended"]`** and **`jest.configs["flat/style"]`** (the
+  `flat/`-prefixed keys are the flat-config ones; unprefixed keys are legacy `.eslintrc`).
+- Rules assume test files, so the README says it's *"generally not suitable to include them in your
+  top-level configuration"* — scope with `files`/`ignores`.
+- **Type-aware `unbound-method`**: the README notes *"`unbound-method` depends on
+  `@typescript-eslint/eslint-plugin`, as it extends the original `unbound-method` rule."* To use it you
+  need `@typescript-eslint/parser` with type info, and you turn off the base rule in favour of
+  `jest/unbound-method`.
+- The README shows both legacy `.eslintrc` and flat config.
 
-## Official docs
+## Source
 
-- eslint-plugin-jest: https://github.com/jest-community/eslint-plugin-jest
+- https://github.com/jest-community/eslint-plugin-jest

package/templates/skills/cbp-setup-eslint/reference/nestjs.md

@@ -1,69 +1,68 @@
-# nestjs — NestJS back-end flat config
+# nestjs — NestJS (official starter ESLint config)
 
-For NestJS apps (the CBP `apps/backend`). **Gap stack — no CBP DB preset.** Use this doc to
-hand-author `eslint.config.mjs`; the `base` + `node` presets cover most of it, but the
-official Nest starter has a specific shape worth matching.
+> **Official source**: https://github.com/nestjs/typescript-starter/blob/master/eslint.config.mjs
+> (verified 2026-05-31). This is the `eslint.config.mjs` the official Nest starter ships, **verbatim**.
 
-> **Verified 2026-05-31.** There is **no first-party NestJS ESLint plugin** — the official
-> `nest new` starter uses plain type-checked `typescript-eslint` + Prettier.
+NestJS has no first-party ESLint plugin — the official starter uses type-checked typescript-eslint +
+Prettier.
 
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `typescript-eslint` | `8.60.0` | parser + type-checked preset |
-| `@eslint/js` | `10.0.1` | `eslint.configs.recommended` |
-| `eslint-plugin-prettier` | `^5` | `/recommended` subpath |
-| `globals` | `17.6.0` | `globals.node`, `globals.jest` |
+## Install
 
 ```bash
-pnpm add -D typescript-eslint @eslint/js eslint-plugin-prettier eslint-config-prettier globals
+npm install --save-dev eslint @eslint/js typescript-eslint eslint-plugin-prettier eslint-config-prettier globals
 ```
 
-## Flat config (official `nest new` starter, verbatim)
+## eslint.config.mjs (official `nest new` starter, verbatim)
 
 ```js
 // @ts-check
-import eslint from "@eslint/js";
-import eslintPluginPrettierRecommended from "eslint-plugin-prettier/recommended";
-import globals from "globals";
-import tseslint from "typescript-eslint";
+import eslint from '@eslint/js';
+import eslintPluginPrettierRecommended from 'eslint-plugin-prettier/recommended';
+import globals from 'globals';
+import tseslint from 'typescript-eslint';
 
 export default tseslint.config(
-  { ignores: ["eslint.config.mjs"] },
+  {
+    ignores: ['eslint.config.mjs'],
+  },
   eslint.configs.recommended,
   ...tseslint.configs.recommendedTypeChecked,
   eslintPluginPrettierRecommended,
   {
     languageOptions: {
-      globals: { ...globals.node, ...globals.jest },
-      sourceType: "commonjs", // "module" for an ESM Nest app
-      parserOptions: { projectService: true, tsconfigRootDir: import.meta.dirname },
+      globals: {
+        ...globals.node,
+        ...globals.jest,
+      },
+      sourceType: 'commonjs',
+      parserOptions: {
+        projectService: true,
+        tsconfigRootDir: import.meta.dirname,
+      },
     },
   },
   {
     rules: {
-      "@typescript-eslint/no-explicit-any": "off",
-      "@typescript-eslint/no-floating-promises": "warn",
-      "@typescript-eslint/no-unsafe-argument": "warn",
-      "prettier/prettier": ["error", { endOfLine: "auto" }],
+      '@typescript-eslint/no-explicit-any': 'off',
+      '@typescript-eslint/no-floating-promises': 'warn',
+      '@typescript-eslint/no-unsafe-argument': 'warn',
+      'prettier/prettier': ['error', { endOfLine: 'auto' }],
     },
   },
 );
 ```
 
-## Gotchas
+## Notes (from the official starter file)
 
-- Nest relaxes three type-checked rules (`no-explicit-any` off; `no-floating-promises` and
-  `no-unsafe-argument` to `warn`) because its DI/decorator patterns trip them. Keep these.
-- `{ ignores: ["eslint.config.mjs"] }` keeps type-aware linting off the config file itself.
-- `sourceType: "commonjs"` matches Nest's default CJS build — flip to `"module"` for ESM.
-- The starter still uses `tseslint.config(...)`; you may swap it for `defineConfig` from
-  `eslint/config` (deprecation note in [base.md](base.md)) — the presets are identical.
-- Optional community add-on: `@darraghor/eslint-plugin-nestjs-typed` adds
-  decorator/Swagger/DTO-aware rules. Not part of the official starter.
-- Nest tests use **Jest** — add the [jest.md](jest.md) override scoped to `**/*.spec.ts`.
+- This is the one official config that wraps with **`tseslint.config(...)`** (not `defineConfig`). It
+  imports `@eslint/js` as `eslint` (so `eslint.configs.recommended`) and spreads
+  `...tseslint.configs.recommendedTypeChecked` (it's an array).
+- `{ ignores: ['eslint.config.mjs'] }` keeps type-aware linting off the config file itself.
+- `sourceType: 'commonjs'` matches Nest's default CJS build — switch to `'module'` for an ESM Nest app.
+- The starter deliberately relaxes three type-checked rules (`no-explicit-any` off;
+  `no-floating-promises` and `no-unsafe-argument` to `warn`) for Nest's DI/decorator patterns, and adds
+  Prettier via `eslint-plugin-prettier/recommended`.
 
-## Official docs
+## Source
 
-- Starter config: https://github.com/nestjs/typescript-starter/blob/master/eslint.config.mjs
+- https://github.com/nestjs/typescript-starter/blob/master/eslint.config.mjs