Hello, our team has been following the FSD methodology for quite some time now, but never committed to using related linting tools.

With the rise of the agentic approach, it has become harder and harder to track minor violations of established rules in large chunks of LLM generated code. Thus, the right mitigation step seems to be programmatic restriction i.e., linting.

The first point of confusion came from the ESLint rules, which apparently represent only a fraction of the Steiger ruleset and are not kept up to date, with the latest change dating back 2 years ago.

Regarding Steiger itself, some of the issues that are alarming at first glance have been left open for over a year with no progress. This raises concerns about maintainability, current and future stability, as well as the overall purpose of the tool.

Additionally, there is no IDE integration, which complicates the DX even further compared to the well-established ESLint rules pattern. The steiger-vscode repo appears to be a 2 year old fork of the Biome repo with no additions.

Based on everything mentioned, the answer to the title could be inferred, yet it would be better to hear it from the maintainers directly.