Custom Linter Creator

Prefer the host language's existing linter ecosystem. The diagnostic message is part of the design: it should be a repair prompt, not just a complaint.

Workflow

1. Extract the rule as a precise, statically detectable condition.

2. Pick the native ecosystem: ESLint for TypeScript/JavaScript, pylint for Python, Go analysis/golangci-lint for Go, dylint or Clippy-style tooling for Rust.

3. Create the rule under lints/ with tests or fixtures.

4. Write diagnostics that include the violation, repair steps, scope limits, and rationale.

5. Integrate the rule into the project lint command.

Diagnostic Template

Use this shape: Problem: ... Repair: 1. ... 2. ... Scope: ... Rationale: ....