diff --git a/README.md b/README.md
index 01eb6bdfa..2b446eb49 100644
--- a/README.md
+++ b/README.md
@@ -1,14 +1,4 @@
-# Introduction
-
-`eslint-plugin-svelte` is the official [ESLint] plugin for [Svelte].  
-It provides many unique check rules by using the template AST.  
-You can check on the [Online DEMO](https://eslint-online-playground.netlify.app/#eslint-plugin-svelte%20with%20typescript).
-
-> [!NOTE]
-> This document is in development.\
-> Please refer to the document for the version you are using.\
-> For example, <https://github.com/sveltejs/eslint-plugin-svelte/blob/eslint-plugin-svelte%402.46.0/README.md>
-> and <https://github.com/sveltejs/eslint-plugin-svelte/blob/eslint-plugin-svelte%402.46.0/docs>
+<!--DOCS_IGNORE_START-->
 
 [![NPM license](https://img.shields.io/npm/l/eslint-plugin-svelte.svg)](https://www.npmjs.com/package/eslint-plugin-svelte)
 [![NPM version](https://img.shields.io/npm/v/eslint-plugin-svelte.svg)](https://www.npmjs.com/package/eslint-plugin-svelte)
@@ -24,253 +14,224 @@ You can check on the [Online DEMO](https://eslint-online-playground.netlify.app/
 [![Code Style: Prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg)](https://github.com/prettier/prettier)
 [![changesets](https://img.shields.io/badge/maintained%20with-changesets-176de3.svg)](https://github.com/atlassian/changesets)
 
-## :name_badge: What is this plugin?
-
-[ESLint] plugin for [Svelte].  
-It provides many unique check rules using the AST generated by [svelte-eslint-parser].
-
-### ❗ Attention
-
-#### Cannot be used with eslint-plugin-svelte3
-
-The [svelte-eslint-parser] and the `eslint-plugin-svelte` can not be used with the [eslint-plugin-svelte3].
+<div align="center">
 
-[svelte-eslint-parser]: https://github.com/sveltejs/svelte-eslint-parser
-[eslint-plugin-svelte3]: https://github.com/sveltejs/eslint-plugin-svelte3
+# eslint-plugin-svelte
 
-#### Experimental support for Svelte v5
+## ESLint plugin for Svelte using AST
 
-We are working on support for Svelte v5, but it is still an experimental feature. Please note that rules and features related to Svelte v5 may be changed or removed in minor versions without notice.
+[Live Demo](https://eslint-online-playground.netlify.app/#eslint-plugin-svelte%20with%20typescript) •
+[Documentation](https://sveltejs.github.io/eslint-plugin-svelte/) •
+[Discord](https://svelte.dev/chat)
 
-<!--DOCS_IGNORE_START-->
-
-## Versioning policy
-
-This plugin follows [Semantic Versioning](https://semver.org/).  
-However, unlike [ESLint’s Semantic Versioning Policy](https://github.com/eslint/eslint#semantic-versioning-policy), this plugin adds new rules to its configs even in minor releases. For example, if you are using the recommended config, a minor update may add new rules, which could cause new lint errors in your project.  
-While [ESLint’s Semantic Versioning Policy](https://github.com/eslint/eslint#semantic-versioning-policy) only adds new rules to configs in major releases, most users (myself included) don’t regularly monitor new rules. This makes it challenging to manually add them to projects whenever they are introduced.  
-By adding new rules to configs in minor releases, this plugin ensures users can adopt them more easily. If any new rules cause issues, you can simply disable them. I believe this approach helps maintain and improve code quality with minimal effort.
-
-## Migration Guide
+</div>
 
-To migrate from `eslint-plugin-svelte` v1, or [`@ota-meshi/eslint-plugin-svelte`](https://www.npmjs.com/package/@ota-meshi/eslint-plugin-svelte), please refer to the [migration guide](https://sveltejs.github.io/eslint-plugin-svelte/migration/).
+<!--DOCS_IGNORE_END-->
 
-## :book: Documentation
+## Introduction
 
-See [documents](https://sveltejs.github.io/eslint-plugin-svelte/).
+`eslint-plugin-svelte` is the official [ESLint](https://eslint.org/) plugin for [Svelte](https://svelte.dev/).  
+It leverages the AST generated by [svelte-eslint-parser](https://github.com/sveltejs/svelte-eslint-parser) to provide custom linting for Svelte.  
+Note that `eslint-plugin-svelte` and `svelte-eslint-parser` cannot be used alongside [eslint-plugin-svelte3](https://github.com/sveltejs/eslint-plugin-svelte3).
 
-## :cd: Installation
+## Installation
 
 ```bash
-npm install --save-dev eslint eslint-plugin-svelte svelte
+npm install --save-dev svelte eslint eslint-plugin-svelte globals
 ```
 
-> **Requirements**
+> [!NOTE]
 >
-> - ESLint v8.57.1, v9.0.0 and above
-> - Node.js v18.20.4, v20.18.0, v22.10.0 and above
-
-<!--DOCS_IGNORE_END-->
+> **Requirements:**
+>
+> - ESLint v8.57.1, v9.0.0, and above
+> - Node.js v18.20.4, v20.18.0, v22.10.0, and above
 
-## :book: Usage
+## Configuration
 
 <!--USAGE_SECTION_START-->
 <!--USAGE_GUIDE_START-->
 
-### Configuration
+Use the `eslint.config.js` file to configure rules. For more details, see the [ESLint documentation](https://eslint.org/docs/latest/use/configure/configuration-files-new).
 
-Use `eslint.config.js` file to configure rules. See also: <https://eslint.org/docs/latest/use/configure/configuration-files-new>.
-
-Example **eslint.config.js**:
+### JavaScript project
 
 ```js
-import eslintPluginSvelte from 'eslint-plugin-svelte';
+// eslint.config.js
+import js from '@eslint/js';
+import svelte from 'eslint-plugin-svelte';
+import globals from 'globals';
+import svelteConfig from './svelte.config.js';
+
+/** @type {import('eslint').Linter.Config[]} */
 export default [
-  // add more generic rule sets here, such as:
-  // js.configs.recommended,
-  ...eslintPluginSvelte.configs.recommended,
+  js.configs.recommended,
+  ...svelte.configs.recommended,
+  {
+    languageOptions: {
+      globals: {
+        ...globals.browser,
+        ...globals.node // Add this if you are using SvelteKit in non-SPA mode
+      }
+    }
+  },
+  {
+    files: [
+      '*.svelte',
+      '**/*.svelte',
+      '*.svelte.ts',
+      '**/*.svelte.ts',
+      '*.svelte.js',
+      '**/*.svelte.js'
+    ],
+    languageOptions: {
+      parserOptions: {
+        // We recommend importing and specifying svelte.config.js.
+        // By doing so, some rules in eslint-plugin-svelte will automatically read the configuration and adjust their behavior accordingly.
+        // While certain Svelte settings may be statically loaded from svelte.config.js even if you don’t specify it,
+        // explicitly specifying it ensures better compatibility and functionality.
+        svelteConfig
+      }
+    }
+  },
   {
     rules: {
-      // override/add rules settings here, such as:
+      // Override or add rule settings here, such as:
       // 'svelte/rule-name': 'error'
     }
   }
 ];
 ```
 
-This plugin provides configs:
-
-- `eslintPluginSvelte.configs.base` ... Configuration to enable correct Svelte parsing.
-- `eslintPluginSvelte.configs.recommended` ... Above, plus rules to prevent errors or unintended behavior.
-- `eslintPluginSvelte.configs.prettier` ... Turns off rules that may conflict with [Prettier](https://prettier.io/) (You still need to configure prettier to work with svelte yourself, for example by using [prettier-plugin-svelte](https://github.com/sveltejs/prettier-plugin-svelte).).
-- `eslintPluginSvelte.configs.all` ... All rules. This configuration is not recommended for production use because it changes with every minor and major version of `eslint-plugin-svelte`. Use it at your own risk.
+### TypeScript project
 
-See [the rule list](https://sveltejs.github.io/eslint-plugin-svelte/rules/) to get the `rules` that this plugin provides.
-
-#### Parser Configuration
-
-If you have specified a parser, you need to configure a parser for `.svelte`.
-
-For example, if you are using the `"@typescript-eslint/parser"`, and if you want to use TypeScript in `<script>` of `.svelte`, you need to add more `parserOptions` configuration.
+```shell
+npm install --save-dev typescript-eslint
+```
 
 ```js
-import eslintPluginSvelte from 'eslint-plugin-svelte';
-import * as svelteParser from 'svelte-eslint-parser';
-import * as typescriptParser from '@typescript-eslint/parser';
-export default [
-  ...js.configs.recommended,
-  ...eslintPluginSvelte.configs.recommended,
+// eslint.config.js
+import js from '@eslint/js';
+import svelte from 'eslint-plugin-svelte';
+import globals from 'globals';
+import ts from 'typescript-eslint';
+import svelteConfig from './svelte.config.js';
+
+export default ts.config(
+  js.configs.recommended,
+  ...ts.configs.recommended,
+  ...svelte.configs.recommended,
   {
-    files: ['**/*.svelte'],
     languageOptions: {
-      parser: svelteParser,
-      parserOptions: {
-        parser: typescriptParser,
-        project: './path/to/your/tsconfig.json',
-        extraFileExtensions: ['.svelte']
+      globals: {
+        ...globals.browser,
+        ...globals.node
       }
     }
-  }
-];
-```
-
-If you have a mix of TypeScript and JavaScript in your project, use a multiple parser configuration.
-
-```js
-import eslintPluginSvelte from 'eslint-plugin-svelte';
-import * as svelteParser from 'svelte-eslint-parser';
-import * as typescriptParser from '@typescript-eslint/parser';
-import espree from 'espree';
-export default [
-  ...js.configs.recommended,
-  ...eslintPluginSvelte.configs.recommended,
+  },
   {
-    files: ['**/*.svelte'],
+    files: ['*.svelte', '**/*.svelte'],
+    // See more details at: https://typescript-eslint.io/packages/parser/
     languageOptions: {
-      parser: svelteParser,
       parserOptions: {
-        parser: {
-          // Specify a parser for each lang.
-          ts: typescriptParser,
-          js: espree,
-          typescript: typescriptParser
-        },
-        project: './path/to/your/tsconfig.json',
-        extraFileExtensions: ['.svelte']
+        projectService: true,
+        extraFileExtensions: ['.svelte'], // Add support for additional file extensions, such as .svelte
+        parser: ts.parser
+        // Specify a parser for each language, if needed:
+        // parser: {
+        //   ts: ts.parser,
+        //   js: espree,    // Use espree for .js files (add: import espree from 'espree')
+        //   typescript: ts.parser
+        // },
       }
     }
-  }
-];
-```
-
-See also <https://github.com/sveltejs/svelte-eslint-parser#readme>.
-
-::: warning ❗ Attention
-
-The TypeScript parser uses a singleton internally and it will only use the
-options given to it when it was first initialized. If trying to change the
-options for a different file or override, the parser will simply ignore the new
-options (which may result in an error). See
-[typescript-eslint/typescript-eslint#6778](https://github.com/typescript-eslint/typescript-eslint/issues/6778)
-for some context.
-
-:::
-
-#### Specify `svelte.config.js`
-
-If you are using `eslint.config.js`, we recommend that you import and specify `svelte.config.js`.
-By specifying it, some rules of `eslint-plugin-svelte` will read it and try to behave well for you by default.
-Some Svelte configurations will be statically loaded from `svelte.config.js` even if you don't specify it, but you need to specify it to make it work better.
-
-Example **eslint.config.js**:
-
-```js
-import eslintPluginSvelte from 'eslint-plugin-svelte';
-import svelteConfig from './svelte.config.js';
-export default [
-  ...eslintPluginSvelte.configs.recommended,
+  },
   {
     files: [
+      '*.svelte',
       '**/*.svelte',
-      '*.svelte'
-      // Add more files if you need.
-      // '**/*.svelte.ts', '*.svelte.ts', '**/*.svelte.js', '*.svelte.js',
+      '*.svelte.ts',
+      '**/*.svelte.ts',
+      '*.svelte.js',
+      '**/*.svelte.js'
     ],
     languageOptions: {
       parserOptions: {
-        // Specify the `svelte.config.js`.
+        // We recommend importing and specifying svelte.config.js.
+        // By doing so, some rules in eslint-plugin-svelte will automatically read the configuration and adjust their behavior accordingly.
+        // While certain Svelte settings may be statically loaded from svelte.config.js even if you don’t specify it,
+        // explicitly specifying it ensures better compatibility and functionality.
         svelteConfig
       }
     }
-  }
-];
-```
-
-#### settings.svelte
-
-You can change the behavior of this plugin with some settings.
-
-e.g.
-
-```js
-export default [
-  // ...
+  },
   {
-    settings: {
-      svelte: {
-        ignoreWarnings: [
-          '@typescript-eslint/no-unsafe-assignment',
-          '@typescript-eslint/no-unsafe-member-access'
-        ],
-        compileOptions: {
-          postcss: {
-            configFilePath: './path/to/my/postcss.config.js'
-          }
-        },
-        kit: {
-          files: {
-            routes: 'src/routes'
-          }
-        }
-      }
+    rules: {
+      // Override or add rule settings here, such as:
+      // 'svelte/rule-name': 'error'
     }
   }
-  // ...
-];
+);
 ```
 
-#### settings.svelte.ignoreWarnings
-
-Specifies an array of rules that ignore reports in the template.  
-For example, set rules on the template that cannot avoid false positives.
+> [!WARNING]
+> The TypeScript parser uses a singleton internally, meaning it only respects the options provided during its initial initialization.
+> If you try to change the options for a different file or override them later, the parser will ignore the new options, which may lead to errors.
+> For more context, see [typescript-eslint/typescript-eslint#6778](https://github.com/typescript-eslint/typescript-eslint/issues/6778).
 
-#### settings.svelte.compileOptions
+### Available Configurations
 
-Specifies options for Svelte compile. Effects rules that use Svelte compile. The target rules are [svelte/valid-compile](https://sveltejs.github.io/eslint-plugin-svelte/rules/valid-compile/) and [svelte/no-unused-svelte-ignore](https://sveltejs.github.io/eslint-plugin-svelte/rules/no-unused-svelte-ignore/). **Note that it has no effect on ESLint's custom parser**.
+This plugin provides the following configurations:
 
-- `postcss` ... Specifies options related to PostCSS. You can disable the PostCSS process by specifying `false`.
-  - `configFilePath` ... Specifies the path of the directory containing the PostCSS configuration.
+- **`eslintPluginSvelte.configs.base`**  
+  Enables correct Svelte parsing.
 
-#### settings.svelte.kit
+- **`eslintPluginSvelte.configs.recommended`**  
+  Includes `base` configuration, plus rules to prevent errors or unintended behavior.
 
-::: warning
+- **`eslintPluginSvelte.configs.prettier`**  
+  Disables rules that may conflict with [Prettier](https://prettier.io/).  
+  You still need to configure Prettier to work with Svelte manually, for example, by using [prettier-plugin-svelte](https://github.com/sveltejs/prettier-plugin-svelte).
 
-Even if you don't specify `settings.svelte.kit`, the rules will try to load information from `svelte.config.js`, so specify `settings.svelte.kit` if the default doesn't work.
+- **`eslintPluginSvelte.configs.all`**  
+  Includes all available rules.  
+  **Note:** This configuration is not recommended for production use, as it changes with every minor and major version of `eslint-plugin-svelte`. Use at your own risk.
 
-:::
+For more details, see [the rule list](https://sveltejs.github.io/eslint-plugin-svelte/rules/) to explore the rules provided by this plugin.
 
-If you use SvelteKit with not default configuration, you need to set below configurations.
-The schema is subset of SvelteKit's configuration.
-Therefore please check [SvelteKit docs](https://kit.svelte.dev/docs/configuration) for more details.
+### settings.svelte
 
-e.g.
+You can customize the behavior of this plugin using specific settings.
 
 ```js
+// eslint.config.js
 export default [
   // ...
   {
     settings: {
       svelte: {
+        // Specifies an array of rules to ignore reports within the template.
+        // For example, use this to disable rules in the template that may produce unavoidable false positives.
+        ignoreWarnings: [
+          '@typescript-eslint/no-unsafe-assignment',
+          '@typescript-eslint/no-unsafe-member-access'
+        ],
+        // Specifies options for Svelte compilation.
+        // This affects rules that rely on Svelte compilation,
+        // such as svelte/valid-compile and svelte/no-unused-svelte-ignore.
+        // Note that this setting does not impact ESLint’s custom parser.
+        compileOptions: {
+          // Specifies options related to PostCSS. You can disable the PostCSS processing by setting it to false.
+          postcss: {
+            // Specifies the path to the directory that contains the PostCSS configuration.
+            configFilePath: './path/to/my/postcss.config.js'
+          }
+        },
+        // Even if settings.svelte.kit is not specified, the rules will attempt to load information from svelte.config.js.
+        // However, if the default behavior does not work as expected, you should specify settings.svelte.kit explicitly.
+        // If you are using SvelteKit with a non-default configuration, you need to set the following options.
+        // The schema is a subset of SvelteKit’s configuration, so refer to the SvelteKit documentation for more details.
+        // https://svelte.dev/docs/kit/configuration
         kit: {
           files: {
             routes: 'src/routes'
@@ -283,15 +244,11 @@ export default [
 ];
 ```
 
-## :computer: Editor Integrations
+## Editor Integrations
 
-### Visual Studio Code
-
-Use the [dbaeumer.vscode-eslint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) extension that Microsoft provides officially.
-
-You have to configure the `eslint.validate` option of the extension to check `.svelte` files, because the extension targets only `*.js` or `*.jsx` files by default.
-
-Example **.vscode/settings.json**:
+**Visual Studio Code**  
+Install [dbaeumer.vscode-eslint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint).  
+Configure `.svelte` files in `.vscode/settings.json`:
 
 ```json
 {
@@ -302,7 +259,17 @@ Example **.vscode/settings.json**:
 <!--USAGE_GUIDE_END-->
 <!--USAGE_SECTION_END-->
 
-## :white_check_mark: Rules
+## Migration Guide
+
+If you’re migrating from `eslint-plugin-svelte` v1 or [`@ota-meshi/eslint-plugin-svelte`](https://www.npmjs.com/package/@ota-meshi/eslint-plugin-svelte), see the [migration guide](https://sveltejs.github.io/eslint-plugin-svelte/migration/).
+
+## Versioning Policy
+
+This project follows [Semantic Versioning](https://semver.org/). Unlike [ESLint’s versioning policy](https://github.com/eslint/eslint#semantic-versioning-policy), new rules may be added in minor releases. If these new rules cause unwanted warnings, you can disable them.
+
+<!--DOCS_IGNORE_END-->
+
+# Rules
 
 <!-- prettier-ignore-start -->
 <!--RULES_SECTION_START-->
@@ -453,23 +420,13 @@ These rules relate to this plugin works:
 
 <!--DOCS_IGNORE_START-->
 
-## :beers: Contributing
-
-Welcome contributing!
-
-Please use GitHub's Issues/PRs.
+## Contributing
 
-See also [CONTRIBUTING.md](./CONTRIBUTING.md)
-
-### Working With Rules
-
-This plugin uses [svelte-eslint-parser](https://github.com/sveltejs/svelte-eslint-parser) for the parser. Check [here](https://sveltejs.github.io/svelte-eslint-parser/) to find out about AST.
+Contributions are welcome! Please open an issue or submit a PR. For more details, see [CONTRIBUTING.md](./CONTRIBUTING.md).  
+Refer to [svelte-eslint-parser](https://github.com/sveltejs/svelte-eslint-parser) for AST details.
 
 <!--DOCS_IGNORE_END-->
 
-## :lock: License
-
-See the [LICENSE](LICENSE) file for license rights and limitations (MIT).
+## License
 
-[svelte]: https://svelte.dev/
-[eslint]: https://eslint.org/
+See [LICENSE](LICENSE) (MIT).
diff --git a/docs/README.md b/docs/README.md
index e7bea45ea..c6aa01a34 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -2,63 +2,45 @@
 title: 'eslint-plugin-svelte'
 ---
 
-# Introduction
+## Introduction
 
-`eslint-plugin-svelte` is the official [ESLint] plugin for [Svelte].  
-It provides many unique check rules by using the template AST.  
-You can check on the [Online DEMO](https://eslint-online-playground.netlify.app/#eslint-plugin-svelte%20with%20typescript).
+`eslint-plugin-svelte` is the official [ESLint](https://eslint.org/) plugin for [Svelte](https://svelte.dev/).  
+It leverages the AST generated by [svelte-eslint-parser](https://github.com/sveltejs/svelte-eslint-parser) to provide custom linting for Svelte.  
+Note that `eslint-plugin-svelte` and `svelte-eslint-parser` cannot be used alongside [eslint-plugin-svelte3](https://github.com/sveltejs/eslint-plugin-svelte3).
 
-> [!NOTE]
-> This document is in development.\
-> Please refer to the document for the version you are using.\
-> For example, <https://github.com/sveltejs/eslint-plugin-svelte/blob/eslint-plugin-svelte%402.46.0/README.md>
-> and <https://github.com/sveltejs/eslint-plugin-svelte/blob/eslint-plugin-svelte%402.46.0/docs>
-
-[![NPM license](https://img.shields.io/npm/l/eslint-plugin-svelte.svg)](https://www.npmjs.com/package/eslint-plugin-svelte)
-[![NPM version](https://img.shields.io/npm/v/eslint-plugin-svelte.svg)](https://www.npmjs.com/package/eslint-plugin-svelte)
-[![NPM downloads](https://img.shields.io/badge/dynamic/json.svg?label=downloads&colorB=green&suffix=/day&query=$.downloads&uri=https://api.npmjs.org//downloads/point/last-day/eslint-plugin-svelte&maxAge=3600)](http://www.npmtrends.com/eslint-plugin-svelte)
-[![NPM downloads](https://img.shields.io/npm/dw/eslint-plugin-svelte.svg)](http://www.npmtrends.com/eslint-plugin-svelte)
-[![NPM downloads](https://img.shields.io/npm/dm/eslint-plugin-svelte.svg)](http://www.npmtrends.com/eslint-plugin-svelte)
-[![NPM downloads](https://img.shields.io/npm/dy/eslint-plugin-svelte.svg)](http://www.npmtrends.com/eslint-plugin-svelte)
-[![NPM downloads](https://img.shields.io/npm/dt/eslint-plugin-svelte.svg)](http://www.npmtrends.com/eslint-plugin-svelte)
-[![Build Status](https://github.com/sveltejs/eslint-plugin-svelte/workflows/CI/badge.svg?branch=main)](https://github.com/sveltejs/eslint-plugin-svelte/actions?query=workflow%3ACI)
-
-[![type-coverage](https://img.shields.io/badge/dynamic/json.svg?label=type-coverage&prefix=%E2%89%A5&suffix=%&query=$.typeCoverage.atLeast&uri=https%3A%2F%2Fraw.githubusercontent.com%2Fsveltejs%2Feslint-plugin-svelte%2Fmain%2Fpackage.json)](https://github.com/plantain-00/type-coverage)
-[![Conventional Commits](https://img.shields.io/badge/conventional%20commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
-[![Code Style: Prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg)](https://github.com/prettier/prettier)
-[![changesets](https://img.shields.io/badge/maintained%20with-changesets-176de3.svg)](https://github.com/atlassian/changesets)
-
-## :name_badge: What is this plugin?
+## Installation
 
-[ESLint] plugin for [Svelte].  
-It provides many unique check rules using the AST generated by [svelte-eslint-parser].
+```bash
+npm install --save-dev svelte eslint eslint-plugin-svelte globals
+```
 
-### ❗ Attention
+> [!NOTE]
+>
+> **Requirements:**
+>
+> - ESLint v8.57.1, v9.0.0, and above
+> - Node.js v18.20.4, v20.18.0, v22.10.0, and above
 
-#### Cannot be used with eslint-plugin-svelte3
+## Configuration
 
-The [svelte-eslint-parser] and the `eslint-plugin-svelte` can not be used with the [eslint-plugin-svelte3].
+See [User Guide](./user-guide.md).
 
-[svelte-eslint-parser]: https://github.com/sveltejs/svelte-eslint-parser
-[eslint-plugin-svelte3]: https://github.com/sveltejs/eslint-plugin-svelte3
+## Migration Guide
 
-#### Experimental support for Svelte v5
+If you’re migrating from `eslint-plugin-svelte` v1 or [`@ota-meshi/eslint-plugin-svelte`](https://www.npmjs.com/package/@ota-meshi/eslint-plugin-svelte), see the [migration guide](./migration.md).
 
-We are working on support for Svelte v5, but it is still an experimental feature. Please note that rules and features related to Svelte v5 may be changed or removed in minor versions without notice.
+## Versioning Policy
 
-## :book: Usage
+This project follows [Semantic Versioning](https://semver.org/). Unlike [ESLint’s versioning policy](https://github.com/eslint/eslint#semantic-versioning-policy), new rules may be added in minor releases. If these new rules cause unwanted warnings, you can disable them.
 
-See [User Guide](./user-guide.md).
+<!--DOCS_IGNORE_END-->
 
-## :white_check_mark: Rules
+# Rules
 
 <!-- prettier-ignore-start -->
 See [Available Rules](./rules.md).
 <!-- prettier-ignore-end -->
 
-## :lock: License
-
-See the [LICENSE](https://github.com/sveltejs/eslint-plugin-svelte/blob/main/LICENSE) file for license rights and limitations (MIT).
+## License
 
-[svelte]: https://svelte.dev/
-[eslint]: https://eslint.org/
+See [LICENSE](https://github.com/sveltejs/eslint-plugin-svelte/blob/main/LICENSE) (MIT).
diff --git a/docs/rules/no-export-load-in-svelte-module-in-kit-pages.md b/docs/rules/no-export-load-in-svelte-module-in-kit-pages.md
index 5c6ccab71..90706a74b 100644
--- a/docs/rules/no-export-load-in-svelte-module-in-kit-pages.md
+++ b/docs/rules/no-export-load-in-svelte-module-in-kit-pages.md
@@ -34,7 +34,7 @@ And the API has changed.
 
 ## :wrench: Options
 
-Nothing. But if you are not using the default routes folder, please set configuration according to the [user guide](../user-guide.md#settings-svelte-kit).
+Nothing. But if you are not using the default routes folder, please set configuration according to the [user guide](../user-guide.md).
 
 ## :books: Further Reading
 
diff --git a/docs/rules/valid-compile.md b/docs/rules/valid-compile.md
index 567ad6c2f..866d2d970 100644
--- a/docs/rules/valid-compile.md
+++ b/docs/rules/valid-compile.md
@@ -50,7 +50,7 @@ export default [
 ];
 ```
 
-See also [User Guide > Specify `svelte.config.js`](../user-guide.md#specify-svelte-config-js)
+See also [User Guide > Configuration](../user-guide.md#configuration)
 
 #### warningFilter
 
diff --git a/docs/rules/valid-prop-names-in-kit-pages.md b/docs/rules/valid-prop-names-in-kit-pages.md
index 7162f4bc3..df56dfc3a 100644
--- a/docs/rules/valid-prop-names-in-kit-pages.md
+++ b/docs/rules/valid-prop-names-in-kit-pages.md
@@ -41,7 +41,7 @@ At SvelteKit v1.0.0-next.405, instead of having multiple props corresponding to
 
 ## :wrench: Options
 
-Nothing. But if use are using not default routes folder, please set configuration according to the [user guide](../user-guide.md#settings-svelte-kit).
+Nothing. But if use are using not default routes folder, please set configuration according to the [user guide](../user-guide.md).
 
 ## :books: Further Reading
 
diff --git a/docs/user-guide.md b/docs/user-guide.md
index eaec31027..4fe436bcf 100644
--- a/docs/user-guide.md
+++ b/docs/user-guide.md
@@ -22,200 +22,186 @@ npm install --save-dev eslint eslint-plugin-svelte svelte
 
 <!--USAGE_GUIDE_START-->
 
-### Configuration
+Use the `eslint.config.js` file to configure rules. For more details, see the [ESLint documentation](https://eslint.org/docs/latest/use/configure/configuration-files-new).
 
-Use `eslint.config.js` file to configure rules. See also: <https://eslint.org/docs/latest/use/configure/configuration-files-new>.
-
-Example **eslint.config.js**:
+### JavaScript project
 
 ```js
-import eslintPluginSvelte from 'eslint-plugin-svelte';
+// eslint.config.js
+import js from '@eslint/js';
+import svelte from 'eslint-plugin-svelte';
+import globals from 'globals';
+import svelteConfig from './svelte.config.js';
+
+/** @type {import('eslint').Linter.Config[]} */
 export default [
-  // add more generic rule sets here, such as:
-  // js.configs.recommended,
-  ...eslintPluginSvelte.configs.recommended,
+  js.configs.recommended,
+  ...svelte.configs.recommended,
+  {
+    languageOptions: {
+      globals: {
+        ...globals.browser,
+        ...globals.node // Add this if you are using SvelteKit in non-SPA mode
+      }
+    }
+  },
+  {
+    files: [
+      '*.svelte',
+      '**/*.svelte',
+      '*.svelte.ts',
+      '**/*.svelte.ts',
+      '*.svelte.js',
+      '**/*.svelte.js'
+    ],
+    languageOptions: {
+      parserOptions: {
+        // We recommend importing and specifying svelte.config.js.
+        // By doing so, some rules in eslint-plugin-svelte will automatically read the configuration and adjust their behavior accordingly.
+        // While certain Svelte settings may be statically loaded from svelte.config.js even if you don’t specify it,
+        // explicitly specifying it ensures better compatibility and functionality.
+        svelteConfig
+      }
+    }
+  },
   {
     rules: {
-      // override/add rules settings here, such as:
+      // Override or add rule settings here, such as:
       // 'svelte/rule-name': 'error'
     }
   }
 ];
 ```
 
-This plugin provides configs:
-
-- `eslintPluginSvelte.configs.base` ... Configuration to enable correct Svelte parsing.
-- `eslintPluginSvelte.configs.recommended` ... Above, plus rules to prevent errors or unintended behavior.
-- `eslintPluginSvelte.configs.prettier` ... Turns off rules that may conflict with [Prettier](https://prettier.io/) (You still need to configure prettier to work with svelte yourself, for example by using [prettier-plugin-svelte](https://github.com/sveltejs/prettier-plugin-svelte).).
-- `eslintPluginSvelte.configs.all` ... All rules. This configuration is not recommended for production use because it changes with every minor and major version of `eslint-plugin-svelte`. Use it at your own risk.
-
-See [the rule list](./rules.md) to get the `rules` that this plugin provides.
+### TypeScript project
 
-#### Parser Configuration
-
-If you have specified a parser, you need to configure a parser for `.svelte`.
-
-For example, if you are using the `"@typescript-eslint/parser"`, and if you want to use TypeScript in `<script>` of `.svelte`, you need to add more `parserOptions` configuration.
+```shell
+npm install --save-dev typescript-eslint
+```
 
 ```js
-import eslintPluginSvelte from 'eslint-plugin-svelte';
-import * as svelteParser from 'svelte-eslint-parser';
-import * as typescriptParser from '@typescript-eslint/parser';
-export default [
-  ...js.configs.recommended,
-  ...eslintPluginSvelte.configs.recommended,
+// eslint.config.js
+import js from '@eslint/js';
+import svelte from 'eslint-plugin-svelte';
+import globals from 'globals';
+import ts from 'typescript-eslint';
+import svelteConfig from './svelte.config.js';
+
+export default ts.config(
+  js.configs.recommended,
+  ...ts.configs.recommended,
+  ...svelte.configs.recommended,
   {
-    files: ['**/*.svelte'],
     languageOptions: {
-      parser: svelteParser,
-      parserOptions: {
-        parser: typescriptParser,
-        project: './path/to/your/tsconfig.json',
-        extraFileExtensions: ['.svelte']
+      globals: {
+        ...globals.browser,
+        ...globals.node
       }
     }
-  }
-];
-```
-
-If you have a mix of TypeScript and JavaScript in your project, use a multiple parser configuration.
-
-```js
-import eslintPluginSvelte from 'eslint-plugin-svelte';
-import * as svelteParser from 'svelte-eslint-parser';
-import * as typescriptParser from '@typescript-eslint/parser';
-import espree from 'espree';
-export default [
-  ...js.configs.recommended,
-  ...eslintPluginSvelte.configs.recommended,
+  },
   {
-    files: ['**/*.svelte'],
+    files: ['*.svelte', '**/*.svelte'],
+    // See more details at: https://typescript-eslint.io/packages/parser/
     languageOptions: {
-      parser: svelteParser,
       parserOptions: {
-        parser: {
-          // Specify a parser for each lang.
-          ts: typescriptParser,
-          js: espree,
-          typescript: typescriptParser
-        },
-        project: './path/to/your/tsconfig.json',
-        extraFileExtensions: ['.svelte']
+        projectService: true,
+        extraFileExtensions: ['.svelte'], // Add support for additional file extensions, such as .svelte
+        parser: ts.parser
+        // Specify a parser for each language, if needed:
+        // parser: {
+        //   ts: ts.parser,
+        //   js: espree,    // Use espree for .js files (add: import espree from 'espree')
+        //   typescript: ts.parser
+        // },
       }
     }
-  }
-];
-```
-
-See also <https://github.com/sveltejs/svelte-eslint-parser#readme>.
-
-::: warning ❗ Attention
-
-The TypeScript parser uses a singleton internally and it will only use the
-options given to it when it was first initialized. If trying to change the
-options for a different file or override, the parser will simply ignore the new
-options (which may result in an error). See
-[typescript-eslint/typescript-eslint#6778](https://github.com/typescript-eslint/typescript-eslint/issues/6778)
-for some context.
-
-:::
-
-#### Specify `svelte.config.js`
-
-If you are using `eslint.config.js`, we recommend that you import and specify `svelte.config.js`.
-By specifying it, some rules of `eslint-plugin-svelte` will read it and try to behave well for you by default.
-Some Svelte configurations will be statically loaded from `svelte.config.js` even if you don't specify it, but you need to specify it to make it work better.
-
-Example **eslint.config.js**:
-
-```js
-import eslintPluginSvelte from 'eslint-plugin-svelte';
-import svelteConfig from './svelte.config.js';
-export default [
-  ...eslintPluginSvelte.configs.recommended,
+  },
   {
     files: [
+      '*.svelte',
       '**/*.svelte',
-      '*.svelte'
-      // Add more files if you need.
-      // '**/*.svelte.ts', '*.svelte.ts', '**/*.svelte.js', '*.svelte.js',
+      '*.svelte.ts',
+      '**/*.svelte.ts',
+      '*.svelte.js',
+      '**/*.svelte.js'
     ],
     languageOptions: {
       parserOptions: {
-        // Specify the `svelte.config.js`.
+        // We recommend importing and specifying svelte.config.js.
+        // By doing so, some rules in eslint-plugin-svelte will automatically read the configuration and adjust their behavior accordingly.
+        // While certain Svelte settings may be statically loaded from svelte.config.js even if you don’t specify it,
+        // explicitly specifying it ensures better compatibility and functionality.
         svelteConfig
       }
     }
-  }
-];
-```
-
-#### settings.svelte
-
-You can change the behavior of this plugin with some settings.
-
-e.g.
-
-```js
-export default [
-  // ...
+  },
   {
-    settings: {
-      svelte: {
-        ignoreWarnings: [
-          '@typescript-eslint/no-unsafe-assignment',
-          '@typescript-eslint/no-unsafe-member-access'
-        ],
-        compileOptions: {
-          postcss: {
-            configFilePath: './path/to/my/postcss.config.js'
-          }
-        },
-        kit: {
-          files: {
-            routes: 'src/routes'
-          }
-        }
-      }
+    rules: {
+      // Override or add rule settings here, such as:
+      // 'svelte/rule-name': 'error'
     }
   }
-  // ...
-];
+);
 ```
 
-#### settings.svelte.ignoreWarnings
-
-Specifies an array of rules that ignore reports in the template.  
-For example, set rules on the template that cannot avoid false positives.
+> [!WARNING]
+> The TypeScript parser uses a singleton internally, meaning it only respects the options provided during its initial initialization.
+> If you try to change the options for a different file or override them later, the parser will ignore the new options, which may lead to errors.
+> For more context, see [typescript-eslint/typescript-eslint#6778](https://github.com/typescript-eslint/typescript-eslint/issues/6778).
 
-#### settings.svelte.compileOptions
+### Available Configurations
 
-Specifies options for Svelte compile. Effects rules that use Svelte compile. The target rules are [svelte/valid-compile](./rules/valid-compile.md) and [svelte/no-unused-svelte-ignore](./rules/no-unused-svelte-ignore.md). **Note that it has no effect on ESLint's custom parser**.
+This plugin provides the following configurations:
 
-- `postcss` ... Specifies options related to PostCSS. You can disable the PostCSS process by specifying `false`.
-  - `configFilePath` ... Specifies the path of the directory containing the PostCSS configuration.
+- **`eslintPluginSvelte.configs.base`**  
+  Enables correct Svelte parsing.
 
-#### settings.svelte.kit
+- **`eslintPluginSvelte.configs.recommended`**  
+  Includes `base` configuration, plus rules to prevent errors or unintended behavior.
 
-::: warning
+- **`eslintPluginSvelte.configs.prettier`**  
+  Disables rules that may conflict with [Prettier](https://prettier.io/).  
+  You still need to configure Prettier to work with Svelte manually, for example, by using [prettier-plugin-svelte](https://github.com/sveltejs/prettier-plugin-svelte).
 
-Even if you don't specify `settings.svelte.kit`, the rules will try to load information from `svelte.config.js`, so specify `settings.svelte.kit` if the default doesn't work.
+- **`eslintPluginSvelte.configs.all`**  
+  Includes all available rules.  
+  **Note:** This configuration is not recommended for production use, as it changes with every minor and major version of `eslint-plugin-svelte`. Use at your own risk.
 
-:::
+For more details, see [the rule list](./rules.md) to explore the rules provided by this plugin.
 
-If you use SvelteKit with not default configuration, you need to set below configurations.
-The schema is subset of SvelteKit's configuration.
-Therefore please check [SvelteKit docs](https://kit.svelte.dev/docs/configuration) for more details.
+### settings.svelte
 
-e.g.
+You can customize the behavior of this plugin using specific settings.
 
 ```js
+// eslint.config.js
 export default [
   // ...
   {
     settings: {
       svelte: {
+        // Specifies an array of rules to ignore reports within the template.
+        // For example, use this to disable rules in the template that may produce unavoidable false positives.
+        ignoreWarnings: [
+          '@typescript-eslint/no-unsafe-assignment',
+          '@typescript-eslint/no-unsafe-member-access'
+        ],
+        // Specifies options for Svelte compilation.
+        // This affects rules that rely on Svelte compilation,
+        // such as svelte/valid-compile and svelte/no-unused-svelte-ignore.
+        // Note that this setting does not impact ESLint’s custom parser.
+        compileOptions: {
+          // Specifies options related to PostCSS. You can disable the PostCSS processing by setting it to false.
+          postcss: {
+            // Specifies the path to the directory that contains the PostCSS configuration.
+            configFilePath: './path/to/my/postcss.config.js'
+          }
+        },
+        // Even if settings.svelte.kit is not specified, the rules will attempt to load information from svelte.config.js.
+        // However, if the default behavior does not work as expected, you should specify settings.svelte.kit explicitly.
+        // If you are using SvelteKit with a non-default configuration, you need to set the following options.
+        // The schema is a subset of SvelteKit’s configuration, so refer to the SvelteKit documentation for more details.
+        // https://svelte.dev/docs/kit/configuration
         kit: {
           files: {
             routes: 'src/routes'
@@ -228,15 +214,11 @@ export default [
 ];
 ```
 
-## :computer: Editor Integrations
+## Editor Integrations
 
-### Visual Studio Code
-
-Use the [dbaeumer.vscode-eslint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) extension that Microsoft provides officially.
-
-You have to configure the `eslint.validate` option of the extension to check `.svelte` files, because the extension targets only `*.js` or `*.jsx` files by default.
-
-Example **.vscode/settings.json**:
+**Visual Studio Code**  
+Install [dbaeumer.vscode-eslint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint).  
+Configure `.svelte` files in `.vscode/settings.json`:
 
 ```json
 {
@@ -248,10 +230,6 @@ Example **.vscode/settings.json**:
 
 ## :question: FAQ
 
-### Parsing the `.svelte` file fails
-
-You should check the [parser configuration](#parser-configuration).
-
 ### You're using TypeScript and the imported `*.svelte` component types cannot be resolved or appear to be
 
 You can try [typescript-eslint-parser-for-extra-files]. Note however that it is still an experimental package.\
diff --git a/packages/eslint-plugin-svelte/src/meta.ts b/packages/eslint-plugin-svelte/src/meta.ts
index 20bdb2225..c68f06541 100644
--- a/packages/eslint-plugin-svelte/src/meta.ts
+++ b/packages/eslint-plugin-svelte/src/meta.ts
@@ -1,5 +1,7 @@
-// IMPORTANT!
-// This file has been automatically generated,
-// in order to update its content execute "pnpm run update"
-export const name = 'eslint-plugin-svelte';
-export const version = '3.0.0-next.16';
+/*
+ * IMPORTANT!
+ * This file has been automatically generated,
+ * in order to update its content execute "pnpm run update"
+ */
+export const name = 'eslint-plugin-svelte' as const;
+export const version = '3.0.0-next.16' as const;
diff --git a/packages/eslint-plugin-svelte/tools/update-readme.ts b/packages/eslint-plugin-svelte/tools/update-readme.ts
index 48e844061..d75ca50aa 100644
--- a/packages/eslint-plugin-svelte/tools/update-readme.ts
+++ b/packages/eslint-plugin-svelte/tools/update-readme.ts
@@ -38,11 +38,12 @@ ${newReadme
 	)
 	.replace(/<!--DOCS_IGNORE_START-->[\s\S]*?<!--DOCS_IGNORE_END-->/gu, '')
 	.replace(
-		/\(https:\/\/sveltejs.github.io\/eslint-plugin-svelte(.*?)\)/gu,
+		/\(https:\/\/sveltejs.github.io\/eslint-plugin-svelte(\/.+)\)/gu,
 		(_ptn, filepath: string) => {
 			const [hash] = /(?:#.*)?$/u.exec(filepath)!;
 			const pathWithoutHash = hash ? filepath.slice(0, -hash.length) : filepath;
 			const normalizePathWithoutHash = pathWithoutHash.replace(/\/$/u, '');
+
 			const [file] = /[^/]+$/u.exec(normalizePathWithoutHash)!;
 			const pathWithoutFile = file
 				? normalizePathWithoutHash.slice(0, -file.length)