codebyplan 1.13.3 → 1.13.5

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

@@ -1,63 +1,62 @@
-# nextjs — Next.js (App Router) flat config
+# nextjs — Next.js (official eslint-config-next setup)
 
-For Next.js apps. Layers on top of [base](base.md). Maps to the CBP **`nextjs`** DB preset
-(`tech_match.requires: ["Next.js"]`, `requires_capabilities: ["jsx"]`).
+> **Official source**: https://nextjs.org/docs/app/api-reference/config/eslint — Next.js **16.2.6**,
+> lastUpdated 2026-05-28. Native ESLint flat config. This is the official setup verbatim.
 
-> **Verified 2026-05-31.** As of **Next.js 16**, `eslint-config-next` ships **native flat
-> config**, `next lint` is **removed** (run `eslint .` directly), and the `eslint` key in
-> `next.config.js` is gone. No `FlatCompat` shim is needed.
-
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `eslint-config-next` | `16.2.6` | bundles `@next/eslint-plugin-next` + react/react-hooks/import |
+## Install
 
 ```bash
-pnpm add -D eslint-config-next
+pnpm add -D eslint eslint-config-next
 ```
 
-## Flat config
+## eslint.config.mjs — TypeScript app
 
-`eslint-config-next` exposes spreadable **array** subpath exports:
+What `create-next-app --typescript` generates:
 
 ```js
-// eslint.config.mjs
 import { defineConfig, globalIgnores } from "eslint/config";
 import nextVitals from "eslint-config-next/core-web-vitals";
 import nextTs from "eslint-config-next/typescript";
 
-export default defineConfig([
-  ...nextVitals, // base + Core-Web-Vitals rules promoted warn→error
-  ...nextTs,     // typescript-eslint rules (based on @typescript-eslint/recommended)
+const eslintConfig = defineConfig([
+  ...nextVitals,
+  ...nextTs,
+  // Override default ignores of eslint-config-next.
   globalIgnores([".next/**", "out/**", "build/**", "next-env.d.ts"]),
 ]);
+
+export default eslintConfig;
 ```
 
-Subpath exports:
-- `eslint-config-next` — base (Next + react + react-hooks recommended).
-- `eslint-config-next/core-web-vitals` — base + CWV rules at error (**recommended default**).
-- `eslint-config-next/typescript` — adds typescript-eslint rules; spread alongside a base.
+JavaScript app: drop the `nextTs` import and the `...nextTs` spread.
 
-## Gotchas
+## Run
 
-- **`globalIgnores([...])` is required** when you spread the config — re-assert the default
-  ignores (`.next/`, etc.) per the official docs example.
-- **Monorepo**: point the plugin at the app with `settings: { next: { rootDir: "apps/web" } }`
-  (path, glob, or array).
-- **Prettier**: add `import prettier from "eslint-config-prettier/flat"` last.
-- `next lint` removal landed in Next 16.0.0 — old `.eslintrc.json` configs should migrate to
-  `eslint.config.mjs` (a codemod exists).
+```bash
+npx eslint .
+```
+
+## The three official configs
 
-## CBP preset divergence
+- **`eslint-config-next`** — base: Next.js + `eslint-plugin-react` + `eslint-plugin-react-hooks`
+  recommended rule-sets (JS + TS).
+- **`eslint-config-next/core-web-vitals`** — base + promotes Core-Web-Vitals rules from warning to
+  error. Recommended default; auto-included by create-next-app.
+- **`eslint-config-next/typescript`** — adds typescript-eslint rules (based on
+  `@typescript-eslint/recommended`); spread alongside one of the above.
 
-CBP's `nextjs` preset pins `eslint-config-next: ^15.0.0` and registers
-`eslint-plugin-react-compiler` explicitly (see [react.md](react.md) — that plugin is now
-**superseded**). The repo's own `apps/web/eslint.config.mjs` already uses the
-`createRequire` + `eslint-config-next/core-web-vitals` + `eslint-config-next/typescript`
-pattern. Adopt the native spread form above when regenerating; presets are not changed by
-this skill.
+## Notes (from the official docs)
+
+- **`next lint` was removed in Next.js v16.0.0** (and the `eslint` option in `next.config.js`). Use
+  the ESLint CLI directly (`npx eslint .`). A codemod is available to migrate.
+- **`globalIgnores([...])` is required** when you spread the config — it re-asserts
+  eslint-config-next's default ignores.
+- **Monorepo**: tell the plugin where the app is via `settings: { next: { rootDir: "packages/my-app/" } }`
+  (path, glob, or array).
+- **Prettier**: install `eslint-config-prettier`, then add
+  `import prettier from "eslint-config-prettier/flat"` and include `prettier` in the array.
+- **Disable rules**: append a `{ rules: { ... } }` object after the spreads.
 
-## Official docs
+## Source
 
-- ESLint config: https://nextjs.org/docs/app/api-reference/config/eslint
+- https://nextjs.org/docs/app/api-reference/config/eslint

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

@@ -1,74 +1,45 @@
-# node — Node/TypeScript service (Hono, Express, plain Node) flat config
+# node — Node.js (official eslint-plugin-n setup)
 
-For Node back-end services and server-side packages (the CBP MCP server uses Hono; any
-`node-server` capability). Layers on [base](base.md). Maps to the CBP **`node`** DB preset
-(`tech_match.requires: ["Node.js"]`, `requires_capabilities: ["node-server"]`).
+> **Official source**: https://github.com/eslint-community/eslint-plugin-n (verified 2026-05-31).
+> ESLint flat config. This is the plugin's official setup verbatim.
 
-> **Verified 2026-05-31.** The valuable async-safety rules (`no-floating-promises`,
-> `no-misused-promises`) are **typescript-eslint** rules that need type info — they come from
-> `recommendedTypeChecked`, not from a node plugin.
+For Node.js services and packages. `eslint-plugin-n` is the maintained Node plugin (successor to the
+deprecated `eslint-plugin-node`).
 
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `globals` | `17.6.0` | `globals.node` |
-| `typescript-eslint` | `8.60.0` | type-aware promise rules |
-| `eslint-plugin-n` | `18.0.1` | **optional** — unsupported-Node-API / import / engines checks |
+## Install
 
 ```bash
-pnpm add -D globals typescript-eslint
-# optional (libraries / dual ESM-CJS packages):
-pnpm add -D eslint-plugin-n
+npm install --save-dev eslint eslint-plugin-n
 ```
 
-## Flat config
+## eslint.config.mjs — ES Modules
 
 ```js
-// eslint.config.mjs
+import node from "eslint-plugin-n";
 import { defineConfig } from "eslint/config";
-import js from "@eslint/js";
-import tseslint from "typescript-eslint";
-import globals from "globals";
-// optional: import n from "eslint-plugin-n";
 
 export default defineConfig([
-  js.configs.recommended,
-  ...tseslint.configs.recommendedTypeChecked, // enables the promise rules below
   {
-    files: ["**/*.{ts,mts,cts}"],
-    languageOptions: {
-      globals: globals.node,
-      sourceType: "module", // "commonjs" for a CJS service
-      parserOptions: { projectService: true, tsconfigRootDir: import.meta.dirname },
-    },
-    rules: {
-      "@typescript-eslint/no-floating-promises": "error",
-      "@typescript-eslint/no-misused-promises": "error",
-    },
+    plugins: { n: node },
+    extends: ["n/recommended-module"],
   },
-  // optional eslint-plugin-n:
-  // { files: ["**/*.{ts,mts,cts}"], plugins: { n }, extends: ["n/recommended-module"] },
 ]);
 ```
 
-## Gotchas
-
-- **`eslint-plugin-n` is optional.** For a pure internal TS service you can skip it — its main
-  value is catching unsupported Node APIs, missing imports, and `package.json#engines` issues
-  in **libraries** and dual ESM/CJS packages. Pick the right preset: `n/recommended-module`
-  (ESM), `n/recommended-script` (CJS), `n/recommended` (mixed).
-- The promise rules **require** a type-checked config + `projectService` — they silently do
-  nothing without type info.
-- A CJS service uses `sourceType: "commonjs"`; an ESM service uses `"module"`.
-
-## CBP preset divergence
+## Notes (from the official docs)
 
-CBP's `node` preset ships only the two `@typescript-eslint` promise rules at `error` (no
-`eslint-plugin-n`). The repo's MCP server / CLI configs follow this minimal shape. Add
-`eslint-plugin-n` per-repo if you publish a library; the skill does not modify the preset.
+- Preset variants (swap the `extends` value):
+  - **`n/recommended-module`** — considers all files as ES Modules.
+  - **`n/recommended-script`** — considers all files as CommonJS.
+  - **`n/recommended`** — handles both; uses `package.json` `"type"` plus `.mjs`/`.cjs` extensions to
+    decide how to treat each file.
+  - **`n/mixed-esm-and-cjs`** — for a package that mixes both.
+- The README uses the `plugins: { n: node }` + `extends: [...]` form, which requires `defineConfig`
+  from `eslint/config`.
+- For a TypeScript Node project, layer this on top of the official typescript-eslint setup
+  ([base.md](base.md)) — the type-aware promise rules (`no-floating-promises`, `no-misused-promises`)
+  come from typescript-eslint's `recommendedTypeChecked`, not from eslint-plugin-n.
 
-## Official docs
+## Source
 
-- eslint-plugin-n: https://github.com/eslint-community/eslint-plugin-n
-- no-floating-promises: https://typescript-eslint.io/rules/no-floating-promises/
+- https://github.com/eslint-community/eslint-plugin-n

package/templates/skills/cbp-setup-eslint/reference/react-native.md

@@ -1,60 +1,56 @@
-# react-native — React Native / Expo flat config
+# react-native — Expo / React Native (official eslint-config-expo setup)
 
-For Expo / React Native apps (the CBP `livebyplan` mobile app). **Gap stack — no CBP DB
-preset.** Use Expo's official lint config.
+> **Official source**: https://docs.expo.dev/guides/using-eslint/ (verified 2026-05-31). This is
+> Expo's official ESLint setup verbatim. Flat config is the default from **Expo SDK 53** onward (SDK 52
+> and earlier use legacy `.eslintrc`).
 
-> **Verified 2026-05-31.** `eslint-config-expo` is the official config and ships **flat config
-> by default from Expo SDK 53** onward (SDK 52 and earlier use legacy `.eslintrc`).
-
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `eslint-config-expo` | `56.0.4` | Expo's flat config (`/flat` subpath) |
+## Setup
 
 ```bash
-npx expo lint   # installs eslint + eslint-config-expo and scaffolds eslint.config.js
+npx expo lint
 ```
 
-`eslint-config-expo` bundles `eslint-plugin-expo`, `eslint-plugin-react`,
-`eslint-plugin-react-hooks`, `eslint-plugin-import`, and `@typescript-eslint/*`. It does **not**
-bundle `eslint-plugin-react-native` (that's a separate optional add-on, `@5.0.0`).
+This generates an **`eslint.config.js`** that extends `eslint-config-expo` and installs the deps on
+first run. Optional Prettier integration:
 
-## Flat config
+```bash
+npx expo install prettier eslint-config-prettier eslint-plugin-prettier --dev
+```
 
-Expo's template is **CommonJS `eslint.config.js`** (not `.mjs`):
+## eslint.config.js (official example, with Prettier)
 
 ```js
-// eslint.config.js
-const { defineConfig } = require("eslint/config");
-const expoConfig = require("eslint-config-expo/flat");
-const eslintPluginPrettierRecommended = require("eslint-plugin-prettier/recommended");
+const { defineConfig } = require('eslint/config');
+const expoConfig = require('eslint-config-expo/flat');
+const eslintPluginPrettierRecommended = require('eslint-plugin-prettier/recommended');
 
 module.exports = defineConfig([
   expoConfig,
   eslintPluginPrettierRecommended,
-  { ignores: ["dist/*"] },
+  {
+    ignores: ['dist/*'],
+  },
 ]);
 ```
 
-Minimal form (no Prettier): just `expoConfig` in the array.
+The bare generated config simply extends `eslint-config-expo/flat`; the block above is the documented
+full example including Prettier. Note Expo's template is **CommonJS `eslint.config.js`**.
 
-## Gotchas
+## Run
 
-- RN platform support comes from RN global variables + platform file extensions
-  (`.android.ts`, `.ios.ts`, `.web.ts`) and `eslint-plugin-expo` — **not** from
-  `eslint-plugin-react-native`. Add `eslint-plugin-react-native@5.0.0` manually only if you
-  want RN-specific rules (`no-inline-styles`, `no-unused-styles`).
-- Run linting with `npx expo lint` (it wires the config the first time).
-- Expo apps test with **Jest** — add the [jest.md](jest.md) override.
+```bash
+npx expo lint
+```
 
-## CBP preset divergence
+## Notes (from the official docs)
 
-There is **no** CBP `react-native`/`expo` DB preset, and the `react` preset `excludes`
-nothing for RN but is browser-globals oriented. Use `eslint-config-expo/flat` directly; the
-skill does not add a preset for this stack.
+- **Flat config availability**: *"From SDK 53 onwards, the default ESLint config file uses the Flat
+  config format. For SDK 52 and earlier, the default ESLint config file uses legacy config and does not
+  support Flat config."*
+- **Prettier**: after setup, *"when you run `npx expo lint`, anything that is not aligned with Prettier
+  formatting will be caught as an error."*
+- **Performance**: for large projects, add a `.eslintignore` with `/.expo` and `node_modules`.
 
-## Official docs
+## Source
 
-- Using ESLint in Expo: https://docs.expo.dev/guides/using-eslint/
-- eslint-config-expo: https://github.com/expo/expo/tree/main/packages/eslint-config-expo
+- https://docs.expo.dev/guides/using-eslint/

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

@@ -1,82 +1,57 @@
-# react — standalone React (Vite, Tauri) flat config
+# react — standalone React (official eslint-plugin-react + react-hooks + jsx-a11y)
 
-For React apps that are **not** Next.js (Vite SPA, Tauri desktop webview). Layers on
-[base](base.md). Maps to the CBP **`react`** DB preset
-(`tech_match.requires: ["React"]`, `excludes: ["Next.js"]`, `requires_capabilities: ["jsx"]`).
+For React projects that are **not** Next.js (Vite, etc.). Each plugin ships its own official flat
+config; compose them. Setup below uses the official config keys from each plugin's docs (verified
+2026-05-31).
 
-> **Verified 2026-05-31.** **Do NOT install `eslint-plugin-react-compiler`** — it is
-> superseded. React Compiler v1.0 (Oct 2025) merged the compiler lint rules into
-> **`eslint-plugin-react-hooks@7`** under `configs.flat["recommended-latest"]`.
+> **Official sources**:
+> - eslint-plugin-react — https://github.com/jsx-eslint/eslint-plugin-react
+> - react-hooks — https://react.dev/reference/eslint-plugin-react-hooks
+> - jsx-a11y — https://github.com/jsx-eslint/eslint-plugin-jsx-a11y
 
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `eslint-plugin-react` | `7.37.5` | React rules + JSX parsing (`configs.flat.*`) |
-| `eslint-plugin-react-hooks` | `7.1.1` | hooks rules **+ bundled React Compiler rules** |
-| `eslint-plugin-jsx-a11y` | `6.10.2` | accessibility (`flatConfigs.*` — note plural) |
+## Install
 
 ```bash
-pnpm add -D eslint-plugin-react eslint-plugin-react-hooks eslint-plugin-jsx-a11y globals
+npm install --save-dev eslint-plugin-react eslint-plugin-react-hooks eslint-plugin-jsx-a11y globals
 ```
 
-## Flat config
+## eslint.config.mjs
 
 ```js
-// eslint.config.mjs
-import { defineConfig } from "eslint/config";
 import react from "eslint-plugin-react";
 import reactHooks from "eslint-plugin-react-hooks";
 import jsxA11y from "eslint-plugin-jsx-a11y";
 import globals from "globals";
+import { defineConfig } from "eslint/config";
 
 export default defineConfig([
-  react.configs.flat.recommended,                 // namespaced react/, enables JSX parsing
-  react.configs.flat["jsx-runtime"],              // React 17+ automatic JSX transform
-  reactHooks.configs.flat["recommended-latest"],  // hooks + React Compiler rules
-  jsxA11y.flatConfigs.strict,                      // or flatConfigs.recommended
+  react.configs.flat.recommended,       // eslint-plugin-react recommended
+  react.configs.flat["jsx-runtime"],    // React 17+ automatic JSX transform
+  reactHooks.configs.flat.recommended,  // rules-of-hooks + exhaustive-deps
+  jsxA11y.flatConfigs.recommended,      // accessibility (or .strict)
   {
-    files: ["**/*.{js,jsx,ts,tsx}"],
-    languageOptions: { globals: globals.browser },
+    // eslint-plugin-react and jsx-a11y do NOT preset files/globals — set them yourself.
+    files: ["**/*.{js,mjs,cjs,jsx,ts,tsx}"],
+    languageOptions: { globals: { ...globals.browser } },
     settings: { react: { version: "detect" } },
   },
 ]);
 ```
 
-## Gotchas
-
-- **`eslint-plugin-react` flat configs do not set `files` or globals** — add your own
-  `files`/`globals.browser`/`settings.react.version` object (shown above) or you'll get the
-  "React version not specified" warning and no JSX globals.
-- **`eslint-plugin-react-hooks` v7 keys** live under `configs.flat.*`:
-  `recommended` (standard hooks) vs `recommended-latest` (hooks **+ compiler** rules — use
-  this for React 19 + the compiler).
-- **`jsx-a11y` uses `flatConfigs` (plural)** — `jsxA11y.flatConfigs.strict`, a different
-  namespace from react's `configs.flat`.
-
-## Storybook (bonus)
-
-If the app uses Storybook, add `eslint-plugin-storybook@10.4.1`:
-
-```js
-import storybook from "eslint-plugin-storybook";
-// ...spread into the array:
-...storybook.configs["flat/recommended"],
-```
-
-The standalone plugin repo was archived (2025-11); it now lives in the Storybook monorepo but
-the npm name `eslint-plugin-storybook` is unchanged.
-
-## CBP preset divergence
+## Notes (from the official docs)
 
-CBP's `react` preset still depends on `eslint-plugin-react-compiler: ^19.0.0` and registers
-`react-compiler/react-compiler`. The latest guidance removes that plugin and relies on
-`eslint-plugin-react-hooks@7`'s `recommended-latest`. Adopt that when regenerating; the skill
-does not modify the preset.
+- eslint-plugin-react and jsx-a11y: *"Our shareable configs do NOT configure `files` or
+  `languageOptions.globals`"* — you must add them yourself (shown above).
+- For React 17+, add `react.configs.flat["jsx-runtime"]` to disable the old "React must be in scope"
+  rules.
+- **react-hooks**: `configs.flat.recommended` is the standard. The plugin also exposes
+  `configs.flat["recommended-latest"]`, which the React team describes as *"bleeding edge experimental
+  compiler rules"* (the React Compiler rules are bundled into `eslint-plugin-react-hooks`). Opt in only
+  if you want them.
+- **jsx-a11y** exposes `flatConfigs.recommended` and `flatConfigs.strict`.
+- eslint-plugin-react's README writes its examples in CommonJS (`require`/`module.exports`); the config
+  keys above are identical in ESM.
 
-## Official docs
+## Source
 
-- eslint-plugin-react: https://github.com/jsx-eslint/eslint-plugin-react
-- react-hooks: https://react.dev/reference/eslint-plugin-react-hooks
-- React Compiler v1.0: https://react.dev/blog/2025/10/07/react-compiler-1
-- jsx-a11y: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y
+See the three URLs above.

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

@@ -1,64 +1,60 @@
-# tailwind — Tailwind CSS class linting
+# tailwind — Tailwind CSS class linting (eslint-plugin-better-tailwindcss)
 
-For apps using Tailwind CSS (the CBP `tarkur` repo uses Tailwind + shadcn/ui). **Gap stack —
-no CBP DB preset.** Adds class-sorting / validation rules on top of the app's base config.
+> **Tailwind ships no first-party ESLint plugin.** Tailwind's official Editor Setup docs recommend only
+> the IntelliSense extension + the official Prettier class-sorting plugin — no ESLint config. The
+> community-standard plugin is `eslint-plugin-better-tailwindcss` (by schoero); its official setup is
+> below (verified 2026-05-31).
 
-> **Verified 2026-05-31.** Use **`eslint-plugin-better-tailwindcss`** — it is the only plugin
-> with first-class **Tailwind v4** + ESLint 9/10 flat-config support. The original
-> `eslint-plugin-tailwindcss` only handles v4 on an unstable alpha — **avoid it for v4.**
-
-## Packages
-
-| Package | Latest | Tailwind v4? | Verdict |
-| ------- | ------ | ------------ | ------- |
-| `eslint-plugin-better-tailwindcss` | `4.5.0` | **yes (stable)** | **use this** |
-| `eslint-plugin-tailwindcss` | `3.18.3` (v4 only on `4.0.0-alpha`) | beta/as-is | avoid for v4 |
+## Install
 
 ```bash
-pnpm add -D eslint-plugin-better-tailwindcss
+npm i -D eslint-plugin-better-tailwindcss
 ```
 
-Peer deps: `eslint ^7 || ^8 || ^9 || ^10`, `tailwindcss ^3.3.0 || ^4.1.17`. Node ≥ 20.19.
+> Depending on your file flavor (JSX/TSX/Vue/Svelte/Astro/HTML/CSS) you may also need the matching
+> parser — see the plugin's per-parser docs.
 
-## Flat config
+## eslint.config.js — React/JSX (official example)
 
 ```js
-// eslint.config.mjs
+import eslintPluginBetterTailwindcss from "eslint-plugin-better-tailwindcss";
 import { defineConfig } from "eslint/config";
-import betterTailwind from "eslint-plugin-better-tailwindcss";
 
-export default defineConfig([
-  {
-    extends: [betterTailwind.configs["recommended"]],
-    settings: {
-      "better-tailwindcss": {
-        // Tailwind v4: path to the CSS file with `@import "tailwindcss"`
-        entryPoint: "src/app/globals.css",
-        // Tailwind v3 ONLY (omit for v4):
-        // tailwindConfig: "tailwind.config.js",
-      },
+export default defineConfig({
+  // enable all recommended rules
+  extends: [eslintPluginBetterTailwindcss.configs.recommended],
+
+  settings: {
+    "better-tailwindcss": {
+      // tailwindcss 4: path to the CSS entry file (e.g. `src/global.css`)
+      entryPoint: "src/global.css",
+      // tailwindcss 3: path to the tailwind config (e.g. `tailwind.config.js`)
+      // tailwindConfig: "tailwind.config.js",
     },
   },
-]);
-```
-
-## Gotchas
 
-- **`settings.entryPoint` is REQUIRED for Tailwind v4** — it points at the global CSS file
-  containing `@import "tailwindcss"` (v4 has no JS config file). For v3, use `tailwindConfig`
-  instead.
-- **Monorepo**: set `settings["better-tailwindcss"].cwd` per file-group so the plugin resolves
-  `tailwindcss` + the config from the correct project dir when ESLint runs from the repo root.
-- Config presets: `recommended`, `correctness` (errors), `stylistic` (warnings); severity
-  suffixes `-error` / `-warn`.
-- Non-JSX file types (Svelte/Vue/Astro/HTML) need the matching `languageOptions.parser`.
-
-## CBP preset divergence
-
-There is **no** CBP `tailwind` DB preset — Tailwind linting is entirely manual. `tarkur`
-currently has no Tailwind ESLint rules; add the block above to lint class order/validity.
-
-## Official docs
+  languageOptions: {
+    parserOptions: { ecmaFeatures: { jsx: true } },
+  },
+});
+```
 
-- eslint-plugin-better-tailwindcss: https://github.com/schoero/eslint-plugin-better-tailwindcss
-- Settings: https://github.com/schoero/eslint-plugin-better-tailwindcss/blob/main/docs/settings/settings.md
+## Notes (from the official docs)
+
+- The plugin is wired in via **`extends: [...configs.recommended]`** — the official docs do **not** use
+  a literal `plugins: {}` key.
+- **Three configs**: `recommended` (both), `correctness`, `stylistic`. By default stylistic rules are
+  warnings, correctness rules are errors. Append `-error` / `-warn` to change severity (e.g.
+  `recommended-warn`).
+- **`settings` is version-specific**:
+  - **Tailwind v4** → `entryPoint`: path to the CSS file containing `@import "tailwindcss"` (v4 has no
+    JS config file).
+  - **Tailwind v3** → `tailwindConfig`: path to `tailwind.config.js`. The docs state: *"For Tailwind
+    CSS v4 and the css based config, use the `entryPoint` option instead."*
+  - Both paths are relative to the working directory; both are optional with automatic fallback.
+- Legacy `.eslintrc` config names are prefixed `legacy-` (e.g. `legacy-recommended`).
+- Runs under your normal `npx eslint .` — no special command.
+
+## Source
+
+- https://github.com/schoero/eslint-plugin-better-tailwindcss (README + `docs/parsers/*`, `docs/settings/settings.md`)

package/templates/skills/cbp-setup-eslint/reference/testing-react.md

@@ -1,57 +1,48 @@
-# testing-react — Testing Library + jest-dom rules
+# testing-react — Testing Library + jest-dom (official setup)
 
-For React component tests (Testing Library assertions). Layers a **test-scoped** override on
-top of [base](base.md) + the test-runner doc ([vitest](vitest.md) or [jest](jest.md)). Maps to
-the CBP **`testing-react`** DB preset
-(`tech_match.requires: ["React", "Vitest"]`, `requires_capabilities: ["jsx"]`).
+> **Official sources** (verified 2026-05-31):
+> - eslint-plugin-testing-library — https://github.com/testing-library/eslint-plugin-testing-library
+> - eslint-plugin-jest-dom — https://github.com/testing-library/eslint-plugin-jest-dom
 
-> **Verified 2026-05-31.** Both plugins use bracketed `configs['flat/...']` keys and each
-> spreads its own plugin registration — keep them as **separate array entries**.
+For React component tests. Each plugin ships its own framework-scoped flat config.
 
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `eslint-plugin-testing-library` | `7.16.2` | Testing Library best-practices |
-| `eslint-plugin-jest-dom` | `5.5.0` | `@testing-library/jest-dom` matchers |
+## Install
 
 ```bash
-pnpm add -D eslint-plugin-testing-library eslint-plugin-jest-dom
+npm install --save-dev eslint-plugin-testing-library eslint-plugin-jest-dom
 ```
 
-## Flat config
+## eslint.config.mjs (official examples)
 
 ```js
-// eslint.config.mjs
 import testingLibrary from "eslint-plugin-testing-library";
 import jestDom from "eslint-plugin-jest-dom";
 
-const TEST_GLOBS = ["**/*.{test,spec}.{ts,tsx,js,jsx}", "**/__tests__/**/*.{ts,tsx,js,jsx}"];
+const TEST_GLOBS = [/* glob matching your test files */];
 
 export default [
-  { files: TEST_GLOBS, ...testingLibrary.configs["flat/react"] }, // 'flat/dom' for non-React
-  { files: TEST_GLOBS, ...jestDom.configs["flat/recommended"] },
+  {
+    files: TEST_GLOBS,
+    ...testingLibrary.configs["flat/react"], // 'flat/dom' for framework-agnostic
+  },
+  {
+    files: TEST_GLOBS,
+    ...jestDom.configs["flat/recommended"],
+  },
 ];
 ```
 
-## Gotchas
-
-- Keep the two as **separate array entries** — each `...config` spread re-declares its own
-  `plugins`. Merging them into one object means you must hand-combine `plugins` + `rules`.
-- `eslint-plugin-testing-library` framework presets: `flat/react`, `flat/dom` (agnostic),
-  `flat/vue`, `flat/angular`, `flat/svelte`, `flat/marko` — pick **one**.
-- Scope to the **same test globs** as your runner override so the rules don't bleed onto
-  production code.
-- Don't let Playwright e2e specs hit `testing-library/*` rules (e.g.
-  `prefer-screen-queries` mis-fires on Playwright's `page.getByRole`) — scope to `src/**`
-  unit tests, not the e2e dir (see [e2e.md](e2e.md)).
-
-## CBP preset divergence
+## Notes (from the official docs)
 
-The CBP `testing-react` preset matches this (`eslint-plugin-testing-library: ^7.0.0`,
-`eslint-plugin-jest-dom: ^5.0.0`, `flat/react` + `flat/recommended`). No divergence.
+- **Testing Library has NO aggregate `flat/recommended`** — the flat configs are **framework-specific
+  only**: `flat/dom`, `flat/react`, `flat/angular`, `flat/vue`, `flat/svelte`, `flat/marko`. Pick one.
+- **jest-dom** uses `configs["flat/recommended"]`.
+- Both plugins require **you** to supply the test-file glob in `files` — they don't preset it.
+- Both READMEs state their *primary* documentation still uses `.eslintrc`; the flat configs are the
+  `flat/`-prefixed alternatives.
+- Keep these as **separate array entries** — each `...config` spread re-declares its own `plugins`.
 
-## Official docs
+## Source
 
-- testing-library: https://github.com/testing-library/eslint-plugin-testing-library
-- jest-dom: https://github.com/testing-library/eslint-plugin-jest-dom
+- https://github.com/testing-library/eslint-plugin-testing-library
+- https://github.com/testing-library/eslint-plugin-jest-dom