How should a large team properly establish and consistently enforce their own genuinely specific Material Design component usage guidelines and conventions across a genuinely large, actively shared Flutter codebase?

A genuinely large team working together on a shared Flutter codebase benefits considerably from clearly documenting their own specific conventions around exactly which particular Material components should genuinely be used for which specific given situations, such as clearly establishing precisely when to use an ElevatedButton versus a considerably lower emphasis TextButton, wrapping commonly used Material components within their own genuinely custom themed wrapper widgets to properly enforce consistent styling automatically, and using automated static analysis or genuinely custom lint rules specifically to help catch cases where a developer might have accidentally used a raw unstyled Material component directly, rather than properly and consistently using the team's own established, correctly themed wrapper widget instead.

// A custom themed wrapper enforcing the team's own specific button conventions
class PrimaryActionButton extends StatelessWidget {
  @override
  Widget build(BuildContext context) => ElevatedButton(style: teamButtonStyle, onPressed: onPressed, child: child);
}