docs(eslint-config): add Nuxt integration guide and NPM scripts section

Add /eslint-config/nuxt documenting how to compose @pleaseai/eslint-config
with @nuxt/eslint — Quick Setup via nuxi, the standalone:false preset
switch that avoids duplicate JS/TS/Vue plugins, and the withNuxt wrapping
pattern using pleaseai() as the base config.

Also lift the lint / lint:fix npm scripts snippet from the Nuxt page
into the main ESLint Config page, since it applies to every project
and was previously undocumented there.

Author: amondnet

docs/content/1.eslint-config/1.index.md

@@ -76,6 +76,21 @@ export default pleaseai(
 )
 ```
 
+## NPM Scripts
+
+Add the lint commands to your `package.json` script section:
+
+```json [package.json]
+{
+  "scripts": {
+    "lint": "eslint .",
+    "lint:fix": "eslint . --fix"
+  }
+}
+```
+
+Run `npm run lint` to check if the code style is correct, or `npm run lint:fix` to automatically fix issues.
+
 ## Defaults
 
 | Option | Value |

docs/content/1.eslint-config/3.nuxt.md

@@ -0,0 +1,67 @@
+---
+title: Nuxt Integration
+description: Use @pleaseai/eslint-config together with @nuxt/eslint in a Nuxt project.
+---
+
+# Nuxt Integration
+
+[`@nuxt/eslint`](https://eslint.nuxt.com/packages/module) is the official ESLint module for Nuxt. It generates a project-aware flat config at `./.nuxt/eslint.config.mjs` that knows about your auto-imports, components directory, and pages, so ESLint can correctly resolve Nuxt globals without manual rules.
+
+`@pleaseai/eslint-config` composes cleanly with `@nuxt/eslint` — the module supplies the Nuxt-specific rules, and `@pleaseai/eslint-config` provides the rest.
+
+## Quick Setup
+
+Add the module with Nuxi — it installs `@nuxt/eslint` and wires it into `nuxt.config.ts` automatically:
+
+```bash [Terminal]
+npx nuxi@latest module add eslint
+```
+
+This gives you a default setup that pulls in ESLint's JS, TS, and Vue plugins on top of the Nuxt-aware rules.
+
+## Custom Config Presets
+
+By default the module installs the JS, TS, and Vue plugins with their recommended rules. Since `@pleaseai/eslint-config` (via `@antfu/eslint-config`) already covers those, disable the default preset by setting `standalone: false` so the module only emits Nuxt-specific rules:
+
+```ts [nuxt.config.ts]
+export default defineNuxtConfig({
+  modules: [
+    '@nuxt/eslint',
+  ],
+  eslint: {
+    config: {
+      standalone: false,
+    },
+  },
+})
+```
+
+Then create `eslint.config.mjs` that wraps `@pleaseai/eslint-config` with the `withNuxt` helper generated by the module:
+
+```js [eslint.config.mjs]
+// @ts-check
+import pleaseai from '@pleaseai/eslint-config'
+import withNuxt from './.nuxt/eslint.config.mjs'
+
+export default withNuxt(
+  pleaseai({
+    // ...@pleaseai/eslint-config options
+    vue: true,
+  }),
+  // ...your other flat config items
+)
+```
+
+`withNuxt` merges its arguments after the Nuxt-aware rules, so anything you pass (including the `@pleaseai/eslint-config` output) takes precedence over the defaults provided by `@nuxt/eslint`.
+
+## Why `standalone: false`?
+
+Without it, `@nuxt/eslint` and `@pleaseai/eslint-config` both install the JS/TS/Vue plugins, producing duplicate-rule warnings and doubling the resolved config size. Setting `standalone: false` scopes the module down to the parts that only Nuxt knows about (auto-imports, component directory globals, page structure) and lets `@pleaseai/eslint-config` own the language tooling.
+
+## Running ESLint
+
+The standard `lint` / `lint:fix` scripts documented on the [main ESLint Config page](/eslint-config#npm-scripts) work unchanged once `@nuxt/eslint` is wired up.
+
+::note
+See the [`@nuxt/eslint` module docs](https://eslint.nuxt.com/packages/module) for additional options like custom rule overrides, per-directory configs, and dev-mode integration.
+::