Every Mesrai rule, in one place

Child components that are tightly coupled with their parent should include the parent component name as a prefix.

In turbo.json, each task must set dependsOn (e.g., "^build") and outputs (e.g., "dist/"). Require cache:true for build/test/lint pipelines unless explicitly justified.

If a PR adds new TODO/FIXME comments, require a tracking ticket. Preferred formats: `TODO(ABC-123): ...` or `FIXME(ABC-123): ...`. If a ticketing MCP is available, suggest (or create) the ticket and link it in the PR. Avoid leaving untracked TODOs in mainline code.

If the change affects users or operators, update end-user docs/runbooks and add a concise changelog entry in the PR description or designated file.

Ensure that all overridden methods explicitly use the `@Override` annotation.

When introducing or deprecating public APIs, include @since for introductions and @deprecated with migration notes and links for removals.

Use `///` instead of regular comments to properly document Dart classes, methods, and properties for automatic documentation generation.

Check if class and module titles use `CamelCase`. If not, suggest renaming them for consistency.

Replace `static final` with `const` where applicable to enable compile-time evaluation and optimize performance.

Identify occurrences where `== None` or `!= None` is used. Using `is None` and `is not None` is more reliable because it checks identity instead of equality, preventing potential issues with overloaded `__eq__` methods.

`string.Equals()` for checking empty strings is inefficient. Use `string.IsNullOrEmpty()` instead for clarity and performance.

Check if `var` is used only when the variable type is clear and enhances readability. Avoid using `var` when the type is not obvious.

Use <inheritdoc/> to inherit docs for overrides/implementations, but explicitly add <exception> and behavior differences when applicable.

Detect relative imports (e.g., `from .module import x`). Relative imports can break if the project structure changes. Recommend using absolute imports (`from package.module import x`) for better clarity and maintainability.

Alias imports when names overlap with locals or other modules; keep clear, unique identifiers.

Use the time package's types for handling time. For example, represent instants as `time.Time` and durations or time intervals as `time.Duration` instead of raw numeric types (int, int64).

Protect one-time initializations with Mutex or atomic operations (computeIfAbsent/compareAndSet).

Prefer set-based SQL (DELETE/UPDATE with WHERE IN/JOIN) or chunked batches over per-row statements.

Group column/index changes with change_table; use concurrent indexes when needed.

Ensure that list, set, or dictionary comprehensions are not overly complex. If a comprehension includes multiple conditions or nested loops, recommend refactoring to a regular loop for better readability.

Compute expensive derived values once per input set and reuse them rather than recalculating in multiple places.

Error strings should start with a lowercase letter and not end with punctuation. They should state what went wrong in a concise, factual manner (for example, "file not found", not "File not found!").

Functions that perform external calls or long operations should accept a `context.Context` parameter and respect its cancellation. Use context timeouts or cancellation signals to stop work that is no longer needed.

Pass dependencies (clients, sessions, configs) into functions/classes instead of creating them internally.