docs: restructure README for better information architecture and flow

Author: johnsoncodehk

README.md

@@ -24,10 +24,10 @@ TSSLint is architecturally optimized for TypeScript by running directly as a `ts
 ## Key Features
 
 *   **Project-Centric**: Treats the **Project (tsconfig)** as a first-class citizen. This aligns with TypeScript's internal architecture, enabling efficient cross-file type analysis and seamless support for complex monorepos.
-*   **Zero Assumptions**: Comes with no built-in rules. It does not enforce any specific coding style or patterns, leaving full control to the developer.
 *   **High Performance**: Runs as a `tsserver` plugin, sharing the existing `TypeChecker` instance to avoid redundant parsing and type-checking.
-*   **Low Noise**: Violations are reported as "Message" diagnostics, ensuring they don't interfere with actual compiler errors or warnings.
+*   **Zero Assumptions**: Comes with no built-in rules. It does not enforce any specific coding style or patterns, leaving full control to the developer.
 *   **Direct AST Access**: Rule authoring uses native TypeScript APIs directly, without unnecessary abstraction layers.
+*   **Low Noise**: Violations are reported as "Message" diagnostics, ensuring they don't interfere with actual compiler errors or warnings.
 
 ## How It Works
 
@@ -47,6 +47,8 @@ In editors like VSCode, when using extensions like **Vue Official (Volar)**, **M
   <img src="architecture_v2.png" alt="TSSLint Framework Support Diagram" width="700">
 </p>
 
+---
+
 ## Getting Started
 
 ### 1. Install
@@ -88,7 +90,11 @@ export default defineConfig({
     }
     ```
 
-## Rule Example
+---
+
+## Rule Authoring
+
+### Rule Example
 
 ```ts
 // rules/no-debugger.ts
@@ -108,7 +114,7 @@ export default defineRule(({ typescript: ts, file, report }) => {
 });
 ```
 
-## Rule Caching Mechanism
+### Rule Caching Mechanism
 
 TSSLint's high performance is partly due to its intelligent caching strategy, which automatically distinguishes between **Syntax-Aware** and **Type-Aware** rules.
 
@@ -119,6 +125,8 @@ By default, all rule diagnostics are cached. However, the cache is automatically
 
 This automatic differentiation allows TSSLint to maximize performance for simple syntax rules while maintaining correctness for complex type-aware rules.
 
+---
+
 ## CLI Usage
 
 The `@tsslint/cli` package provides a command-line tool for CI/CD and build processes.
@@ -137,10 +145,15 @@ npx tsslint --project packages/*/tsconfig.json --vue-project apps/web/tsconfig.j
 npx tsslint --project {tsconfig.json,packages/*/tsconfig.json,extensions/*/tsconfig.json}
 ```
 
+> [!NOTE]
+> **CLI Caching**: The CLI uses a file system cache to speed up subsequent runs. The cache files are stored in your operating system's temporary directory (`os.tmpdir()`) to avoid polluting your project's file system. The cache path includes the TSSLint version and a project-specific hash to prevent conflicts. The cache is automatically invalidated when the project's `tsslint.config.ts`, the CLI arguments, or the TSSLint version changes.
+
 > [!TIP]
 > TSSLint focuses on diagnostic fixes and does not include a built-in formatter. It is recommended to run a dedicated formatter like **Prettier**, **dprint**, or **oxfmt** after running TSSLint with `--fix`.
 
-## Extensions
+---
+
+## Extensions & Ecosystem
 
 ### Ignoring Rules
 ```ts
@@ -158,6 +171,8 @@ export default defineConfig({
 *   **ESLint**: Convert rules via `@tsslint/eslint`.
 *   **TSLint**: Convert rules via `@tsslint/tslint`.
 
+---
+
 ## Technical Notes
 
 *   **Node.js**: Requires 22.6.0+ (v3.0+).