// library

Every Mesrai rule, in one place

808 rules

Severity

Bucket

Low
Use message keys for error messages
Emit stable message keys (for i18n/observability) and resolve user-facing text via localization layers.
internationalization-i18nobservability-logging
Low
Use Metadata API instead of <Head>
Declare SEO metadata via export const metadata or generateMetadata; avoid manual <Head> in App Router.
stack-nextjsstack-react+2
Low
Use Module Imports Instead of Importing Specific Classes or Functions
Check if the code imports individual classes or functions instead of the entire module. Directly importing specific classes or functions can clutter the titlespace and increase naming conflicts. Recommend importing the module and referencing items explicitly.
module-architecturereadability-refactor+2
Low
Use named constants for magic values
Replace numeric/string literals with named constants to document meaning.
maintainabilityreadability-refactor
Low
Use next/font for fonts (no <link> to external CDNs)
Load fonts via next/font (google or local) and apply on html/body; avoid runtime <link> to fonts that cause FOUT/CLS.
stack-nextjsstack-react+2
Low
Use next/script safely and avoid inline scripts
For third-party scripts, use <Script> with an appropriate strategy and onLoad callbacks. Avoid dangerouslySetInnerHTML for scripts.
stack-nextjsstack-react+2
Low
Use object literals for event payloads
When emitting custom events with data using `$emit`, pass an object literal as the payload instead of a raw primitive value, especially if there's a chance more data might be needed later.
api-conventionsmaintainability+1
Low
Use object/array shorthands and spread syntax
Utilize object method shorthands, property value shorthands, and computed property names when defining objects (e.g., in `data`, `computed`, `methods`). Prefer object spread syntax (`...`) over `Object.assign` for shallow copies or merging objects.
stack-vuestyle-conventions
Low
Use or instead of + for combining queries
Combine ActiveRecord relations with `or` instead of materializing arrays or concatenating results.
performance-efficiency
Low
Use PascalCase for Methods and Properties
Consistent naming conventions improve readability and maintainability. Method and property titles should follow PascalCase.
style-conventions
Low
Use PascalCase for Type Names
Following PascalCase for type titles ensures consistency and readability across the codebase.
style-conventions
Low
Use periodic tasks over per-entry scheduling
For large sets, prefer a periodic sweep job rather than spawning one job/timer per item.
performance-efficiency
Low
Use private access modifiers for encapsulation
Prefer the most restrictive access modifier that works (private/internal) and expose only necessary members.
module-architecturestyle-conventions
Low
Use Promise.allSettled for batch operations with partial failures
For many independent tasks, prefer Promise.allSettled and handle per-item results.
error-handlingresilience-retries-idempotency
Low
Use proper naming conventions
Follow .NET naming: PascalCase for types/methods/properties, camelCase for locals/parameters, and meaningful names.
style-conventions
Low
Use Rails conventions for resource naming
Follow Rails conventions (plural resource routes, model singular class names, snake_case files).
style-conventions
Low
Use redirect() and notFound() from next/navigation
Prefer redirect() and notFound() over manual 302/404 handling and custom components in App Router.
stack-nextjsstack-react+2
Low
Use safe type casting with as operator
Use the as operator or pattern matching for safe casts and guard null results before usage.
error-handlingstyle-conventions
Low
Use Spaces Around Operators
Ensure that arithmetic and logical operators have spaces around them for better readability (e.g., `x + y` instead of `x+y`).
readability-refactorstyle-conventions
Low
Use specific types over overly generic ones
Prefer precise types (long, BigDecimal, LocalDate) over Number/Object when the domain is known.
readability-refactorstyle-conventions
Low
Use standard HTTP status text for errors
Return appropriate status codes and prefer http.StatusText(status) (or a consistent JSON error schema) rather than inventing custom reason phrases.
api-conventionsstyle-conventions
Low
Use static constants for inline collections
Extract repeated inline collections to unmodifiable static constants.
duplication-complexityperformance-efficiency
Low
Use String.replace for literal replacements
Use String#replace for literal substrings instead of replaceAll unless regex is required.
performance-efficiency
Low
Use StringBuilder for string concatenation
Use StringBuilder for many concatenations in loops or when building large strings.
performance-efficiency

Use message keys for error messages

Use Metadata API instead of <Head>

Use Module Imports Instead of Importing Specific Classes or Functions

Use named constants for magic values

Use next/font for fonts (no <link> to external CDNs)

Use next/script safely and avoid inline scripts

Use object literals for event payloads

Use object/array shorthands and spread syntax

Use or instead of + for combining queries

Use PascalCase for Methods and Properties

Use PascalCase for Type Names

Use periodic tasks over per-entry scheduling

Use private access modifiers for encapsulation

Use Promise.allSettled for batch operations with partial failures

Use proper naming conventions

Use Rails conventions for resource naming

Use redirect() and notFound() from next/navigation

Use safe type casting with as operator

Use Spaces Around Operators

Use specific types over overly generic ones

Use standard HTTP status text for errors

Use static constants for inline collections

Use String.replace for literal replacements

Use StringBuilder for string concatenation

Use message keys for error messages

Use Metadata API instead of <Head>

Use Module Imports Instead of Importing Specific Classes or Functions

Use named constants for magic values

Use next/font for fonts (no <link> to external CDNs)

Use next/script safely and avoid inline scripts

Use object literals for event payloads

Use object/array shorthands and spread syntax

Use or instead of + for combining queries

Use PascalCase for Methods and Properties

Use PascalCase for Type Names

Use periodic tasks over per-entry scheduling

Use private access modifiers for encapsulation

Use Promise.allSettled for batch operations with partial failures

Use proper naming conventions

Use Rails conventions for resource naming

Use redirect() and notFound() from next/navigation

Use safe type casting with as operator

Use Spaces Around Operators

Use specific types over overly generic ones

Use standard HTTP status text for errors

Use static constants for inline collections

Use String.replace for literal replacements

Use StringBuilder for string concatenation