// ESLint and Prettier configuration for React/TypeScript frontend and Node.js/TypeScript backend. Load when setting up a new project, adding lint rules, fixing lint errors, or reviewing lint config.
| name | linting |
| description | ESLint and Prettier configuration for React/TypeScript frontend and Node.js/TypeScript backend. Load when setting up a new project, adding lint rules, fixing lint errors, or reviewing lint config. |
| user-invocable | false |
| stack | frontend/react |
Full rules in linting.md. Always-on summary:
Stack (locked — no alternatives):
eslint.config.ts) — never .eslintrc.*eslint-config-prettier — disables all ESLint rules that conflict with Prettierlint-staged + husky — auto-lint on git commitFrontend additions on top of base:
eslint-plugin-react, eslint-plugin-react-hooks, eslint-plugin-jsx-a11yeslint-plugin-react-refresh for Vite HMR safetyeslint-plugin-tailwindcss — class order enforcementBackend additions on top of base:
eslint-plugin-node (or eslint-plugin-n) — Node.js-specific ruleseslint-plugin-security — catches common security anti-patternsRules enforced everywhere:
no-console — error in production code (use pino logger)no-unused-vars — error; _ prefix for intentionally unused@typescript-eslint/no-explicit-any — error; never use any@typescript-eslint/consistent-type-imports — import type for type-only importsno-floating-promises — all Promises must be awaited or explicitly handledNever:
.eslintignore — use ignores array in flat config instead// eslint-disable without a comment explaining whyRelated skills — apply together:
typescript-patterns — strict TS compiler flags align with ESLint strict rulesreact-standards — React-specific hooks rules enforced by react-hooks plugintesting-standards — separate ESLint config for test files (jest/vitest globals)