[all components][docs-infra] Enforce error message format

[oliviertassinari]

Summary

We have this rule when it comes to writing great error messages https://www.notion.so/mui-org/DevEx-Technical-writing-style-guide-7e55b517ac2e489a9ddb6d0f6dd765de#85219822c3194b6f8a49ee08ea82b90a.

Up until now, we couldn't automate our projets to follow it because it required human to determine either the message followed the rule or not. However, we now have LLMs that can do this, at scale, and at a fraction of the resource cost.

So it looks like we should:

• Ask AI agent to go through all the codebase to clean things up.
• If it worked, have some sort of a CI lining rule that can reports mistakes. Maybe AI skills, if token cheap enough or an AST matcher and forward.

Action plan:

• Add rule in Material UI [code-infra] Add initial agent instructions material-ui#47655
• Run rule in Material UI
• Add rule in MUI X
• Run rule in MUI X
• Add rule in Base UI
• Run rule in Base UI
  • Fix [useButton] Capture component stack for nativeButton error message base-ui#3861 (comment)

Examples

No response

Motivation

Similar to #222, improve the DX when things go wrong. Make recovering, for humans, AI easy.

cc @mapache-salvaje

Search keywords: -

[Janpot]

I think we can just update agent instructions. probably no need to write extra software for this. claude code can do a one off review of the codebase, and copilot reviewbot or greptile can make sure it gets flagged on PRs.