sensors_config-typescript

Automated TypeScript code quality monitoring is configured by integrating ESLint, Vitest, and dependency-cruiser to enforce linting, testing, and architectural rules without manual boilerplate. This skill detects your project structure and automatically applies the necessary configurations.

Yes, dependency-cruiser is used to enforce architectural rules and prevent dependency drift in JavaScript projects. The skill analyzes project layers and generates dependency-cruiser rules to maintain architectural integrity.

Setting up ESLint custom formatters that provide actionable developer guidance is achieved by injecting specialized formatters during the automated sensor configuration process. This ensures developers receive direct, actionable feedback from linting results.

Yes, this automated sensor configuration works with existing Vitest and TypeScript setups. It automatically detects the project structure and configures the tools to establish a robust feedback loop for type safety and test coverage.

Generating dependency-cruiser templates to analyze project layers in a TypeScript codebase is handled by the skill's architecture enforcement feature. It analyzes your project structure and automatically generates the necessary dependency rules.

No, you do not need to manually configure Stryker and Semgrep when setting up automated quality sensors. The skill configures these dependencies automatically alongside ESLint, Vitest, and dependency-cruiser based on your project structure.