docs: base Testing Rules documentation

Author: c0sta

Diff for: docs/contributing/local-development/Local_Linking.mdx

@@ -8,6 +8,7 @@ The general strategy to do so is:
 
 1. [Global linking](#global-linking): Use your package manager's global link command to make `@typescript-eslint/*` packages available as global symlinks.
 2. [Repository linking](#repository-linking): Use your package manager's link command to reference those global symlinks in the local downstream repository.
+3. [Testing rules](#testing): Test your local rules and plugins by enabling them in the local downstream repository.
 
 ## Global Linking
 
@@ -45,6 +46,24 @@ Now, you should be able to run ESLint in the local downstream repository as you
 To check that the local package is being used, consider adding a `console.log("Hello, world!");` to a file such as `./packages/eslint-plugin/dist/index.js` and making sure that log appears when linting the local downstream repository.
 :::
 
+## Testing Rules
+
+Now that you've linked the `@typescript-eslint/*` packages with your local downstream repository, the next step would be to include the rule on the local repository ESLint configuration file, e.g:
+
+```json
+{
+  "rules": {
+    "@typescript-eslint/your-awesome-rule": "error"
+  }
+  // etc
+}
+```
+
+After that, you just need to run your repository `lint` script.
+
+- `npm run lint`
+- `yarn lint`
+
 ## Troubleshooting
 
 ### Packages Not Found (`Cannot find module`)