I just realizedhttps://typescript-eslint.io/rules/#extension-rules is probably the only canonical link to an explanation of extension rules out there. So we probably don't want to get rid of the heading. But I've pestered you so much on this PR 😅 I'll just add it in, and if you@Josh-Cena /@Zamiell disagree we can always revert before the release on Monday.

do we really need a separate heading though? it is fairly self-explanatory what an extension rule is.
like, for example, considerclass-methods-use-this.
if you go to the page for it, it says:

This rule extends the baseeslint/class-methods-use-this rule. It adds support for ignoring override methods or methods on classes that implement an interface.

After reading this, i am not left wondering, "I have more questions about what an extension rule is, I wonder if there is a more formal definition out there in a dedicated section?"

I think folks need somewhere to hard-link to. It's similar to ESLint's issue for fixers vs suggestions: even if they're fairly straightforward for many, some folks coming in fresh have a hard time with them. I personally had a hard time both with fixers-vs-suggestionsand what extension rules are.

Ooh and - pretty soon I think we'll be able to trim down the metadata list down to one sentence per item!

• Suggestions: can link todocs: explained rule fixers and suggestions eslint/eslint#17657 once it's in
• Formatting rules:https://eslint.style is coming soon

...which just leaves the deeper explanation on extension rules.