LowFile-scope

Deprecation guardian: prefer the new standard and follow the migration guide

If the PR introduces or expands usage of deprecated libraries/patterns the team is migrating away from (e.g., Moment.js, React Class Components), block and suggest the modern replacement. If the repo includes a migration guide (e.g., `docs/migration.md`, `CONTRIBUTING.md`, `docs/adr/*`), follow it and propose the equivalent snippet. If no guide exists, use an available web/search MCP to propose a safe, modern alternative and ask for confirmation of project standards.

Add to Mesrai Open workspace

Why this matters

Prevents new tech debt and accelerates standardization across the codebase.

Bad vs. good

Side-by-side examples engineers can pattern-match during review.

Avoid

Adds new Moment.js usage in a new feature.

Prefer

Uses date-fns/Luxon or native Intl APIs per migration guide; avoids new class components.

More snippets

Bad

import moment from 'moment'

Good

Use approved date library + follow migration guide

Related rules

From the same buckets as this rule.

Critical
Avoid Duplicating String Literals
Store repeated string literals in constants or variables to improve maintainability and reduce redundancy.
duplication-complexitymaintainability
Critical
Avoid Empty Methods
Detect methods that have an empty body. If a method is empty, ensure that a comment is present explaining why it remains unimplemented.
maintainabilityreadability-refactor
Critical
Avoid modifying built-in prototypes
Detect modifications to built-in prototypes. Modifying built-in objects can lead to compatibility issues and unexpected behavior. Recommend creating helper functions instead.
maintainabilitysecurity-hardening

Why this matters

Bad vs. good

More snippets

Related rules

Avoid Duplicating String Literals

Avoid Empty Methods

Avoid modifying built-in prototypes

Why this matters

Bad vs. good

More snippets

Related rules

Avoid Duplicating String Literals

Avoid Empty Methods

Avoid modifying built-in prototypes