codebyplan 1.13.3 → 1.13.4

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

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

@@ -1,62 +1,42 @@
-# vitest — Vitest test-file rules
+# vitest — Vitest test files (official @vitest/eslint-plugin setup)
 
-For apps that test with Vitest (CBP web + CLI + most repos). Layers a **test-scoped** override
-on top of [base](base.md). Maps to the CBP **`testing`** DB preset
-(`tech_match.requires: ["Vitest"]`).
+> **Official source**: https://github.com/vitest-dev/eslint-plugin-vitest (verified 2026-05-31). This
+> is the plugin's official flat-config example verbatim.
 
-> **Verified 2026-05-31.** The package was **renamed** to the scoped
-> **`@vitest/eslint-plugin`** (the old `eslint-plugin-vitest` is the deprecated name). Its
-> flat-config key is plain **`configs.recommended`** — there is **no `flat/` prefix**.
+> The package was renamed from `eslint-plugin-vitest` to the scoped **`@vitest/eslint-plugin`**.
 
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `@vitest/eslint-plugin` | `1.6.18` | Vitest rules (scoped pkg) |
+## Install
 
 ```bash
-pnpm add -D @vitest/eslint-plugin
+npm install @vitest/eslint-plugin --save-dev
 ```
 
-## Flat config
+## eslint.config.mjs (official example)
 
 ```js
-// eslint.config.mjs
+import { defineConfig } from "eslint/config";
 import vitest from "@vitest/eslint-plugin";
 
-export default [
-  {
-    files: ["**/*.{test,spec}.{ts,tsx,js,jsx}"],
-    plugins: { vitest },
-    rules: {
-      ...vitest.configs.recommended.rules,
-      // tests are I/O-heavy + mock-heavy — relax type-safety on test files:
-      "@typescript-eslint/no-explicit-any": "off",
-      "@typescript-eslint/no-unsafe-assignment": "off",
-      "@typescript-eslint/no-unsafe-member-access": "off",
-      "@typescript-eslint/no-unsafe-call": "off",
-      "@typescript-eslint/no-unsafe-argument": "off",
-      "@typescript-eslint/no-unsafe-return": "off",
-    },
-    settings: { vitest: { typecheck: true } }, // only if using Vitest type-testing
+export default defineConfig({
+  files: ["tests/**"], // or any other pattern
+  plugins: {
+    vitest,
+  },
+  rules: {
+    ...vitest.configs.recommended.rules,
+    "vitest/max-nested-describe": ["error", { max: 3 }],
   },
-];
+});
 ```
 
-## Gotchas
-
-- The key is **`vitest.configs.recommended`** (plain) — NOT `configs['flat/recommended']`.
-  Other plugins use the bracketed `flat/` form; Vitest does not.
-- When you spread only `.rules`, register `plugins: { vitest }` yourself. Alternatively spread
-  the whole `...vitest.configs.recommended` (carries the plugin registration).
-- The `no-unsafe-*` / `no-explicit-any` opt-outs are CBP convention — production code keeps
-  them at `error`; test surfaces relax them because mocks produce `any`-typed values.
-
-## CBP preset divergence
+## Notes (from the official docs)
 
-The CBP `testing` preset matches this (the six `no-unsafe-*`/`no-explicit-any` opt-outs,
-`@vitest/eslint-plugin: ^1.0.0`). No divergence.
+- The config key is **`vitest.configs.recommended`** — there is **no `flat/` prefix** (unlike most
+  other test plugins). Variants: `configs.recommended` and `configs.all`.
+- Register `plugins: { vitest }` yourself when spreading only `.rules`.
+- Scope to your test files via `files`. Vitest type-testing uses a separate `typecheck: true` setting.
+- The README still shows legacy `.eslintrc` JSON for ESLint ≤ v8.57.0 alongside flat config.
 
-## Official docs
+## Source
 
-- @vitest/eslint-plugin: https://github.com/vitest-dev/eslint-plugin-vitest
+- https://github.com/vitest-dev/eslint-plugin-vitest

package/templates/hooks/cbp-notify.sh

@@ -1,68 +0,0 @@
-#!/bin/bash
-# @hook: Notification
-# Hook: Notification for all matchers
-# Purpose: Send desktop notifications with project context. Cross-platform graceful-degrade —
-#          silent no-op when terminal-notifier is missing (Linux/Windows/macOS without Homebrew);
-#          VS Code click-to-focus action only on macOS hosts with `code` on PATH.
-# Exit 0 = always (notification hooks must never block Claude)
-#
-# Known: notification_type is not sent in JSON input (anthropics/claude-code#11964)
-# Input fields: session_id, cwd, hook_event_name, message
-
-set +e
-
-# Graceful skip on hosts without terminal-notifier (Linux, Windows, macOS w/o Homebrew)
-command -v terminal-notifier >/dev/null 2>&1 || exit 0
-
-# Read JSON input from stdin
-INPUT=$(cat)
-
-# Parse notification fields
-eval "$(echo "$INPUT" | jq -r '
-  @sh "MESSAGE=\(.message // "")",
-  @sh "CWD=\(.cwd // "")"
-' 2>/dev/null)"
-
-# Detect project name
-if [ -n "$CLAUDE_PROJECT_DIR" ]; then
-  PROJECT_DIR="$CLAUDE_PROJECT_DIR"
-elif [ -n "$CWD" ]; then
-  PROJECT_DIR="$CWD"
-else
-  PROJECT_DIR="unknown"
-fi
-PROJECT_NAME=$(basename "$PROJECT_DIR")
-
-TITLE="[$PROJECT_NAME] Claude Code"
-BODY="${MESSAGE:-Claude Code notification}"
-
-# VS Code focus click action — only on macOS with `code` available
-CLICK_ACTION=""
-if [[ "$OSTYPE" == darwin* ]] && command -v code >/dev/null 2>&1; then
-  # Quote path for re-parse by terminal-notifier -execute (POSIX sh)
-  SAFE_DIR=$(printf '%q' "$PROJECT_DIR")
-  CLICK_ACTION="code -r $SAFE_DIR && sleep 0.3 && osascript -e 'tell application \"System Events\" to keystroke \"\`\" using control down'"
-fi
-
-# Send notification via terminal-notifier in background (non-blocking).
-# Omit -execute argument entirely when CLICK_ACTION is empty (avoid passing empty string).
-if [ -n "$CLICK_ACTION" ]; then
-  terminal-notifier \
-    -title "$TITLE" \
-    -message "$BODY" \
-    -sound "Glass" \
-    -group "claude-${PROJECT_NAME}" \
-    -execute "$CLICK_ACTION" \
-    -sender "com.microsoft.VSCode" \
-    > /dev/null 2>&1 &
-else
-  terminal-notifier \
-    -title "$TITLE" \
-    -message "$BODY" \
-    -sound "Glass" \
-    -group "claude-${PROJECT_NAME}" \
-    -sender "com.microsoft.VSCode" \
-    > /dev/null 2>&1 &
-fi
-
-exit 0