Motivation
Some motivation is given in #27.

Some config, e.g. ruff rules, are perhaps too advanced for some projects. We could have a level of strictness associated with each tool but that gets coordinated with an overall strictness framework.

I like the idea of motivating the strictness categories with whether a tool is recommended at different development statuses e.g. #122, although I am not sure we would need 7 levels so some statuses might get associated with the same level multiple times.

An interface could be usethis strictness <arg> although I am not sure what the naming system would be.

We could also introduce a --strictness arg to all tools to override the global default, which would be set in pyproject.toml. Probably strictnesses for individual tools could also be set in pyproject.toml in their own individual settings but that might a bit much to begin with.
If a global strictness isn't provided, we would default to a particular development status.

To begin with, all tools would behave the same under the different strictness levels but we should create issues for each one to start to give different behaviours for each one as appropriate.

Summary of desired enhancement
Add an interface for adding strictness.