Ensure that extensions use UpperCamelCase naming conventions (e.g., `MyExtension`). Avoid other casing styles that could reduce readability.
stack-flutterstyle-conventions
Low
DO title import prefixes using lowercase_with_underscores
Check that import prefixes use lowercase_with_underscores (e.g., `my_library`), following Dart's style guide.
stack-flutterstyle-conventions
Low
DO title other identifiers using lowerCamelCase
Ensure that identifiers such as variables and method titles are written in lowerCamelCase (e.g., `myVariable`). Avoid using other naming conventions.
stack-flutterstyle-conventions
Low
DO type annotate fields and top-level variables if the type isn't obvious
Check that fields and top-level variables are type-annotated explicitly when the type is not obvious from the context. This avoids ambiguity.
readability-refactorstack-flutter+1
Low
Document async/Promise behavior and errors
For async functions or functions returning Promise, document resolve value, rejection conditions, and usage with await; include @throws or @returns {Promise<Type>}.
style-conventionsreadability-refactor+1
Low
Document measurable acceptance criteria
Include clear, testable success metrics or SLOs in ADRs (e.g., p95 latency < 120ms, error rate < 0.1%) under a 'Measures of Success' section.
docs-adrsperformance-efficiency
Low
DOM elements should use the autocomplete attribute correctly
Check for missing or incorrect autocomplete attributes. Proper use of autocomplete improves accessibility and usability, especially for screen readers.
accessibility-a11ysecurity-hardening
Low
DON'T explicitly title libraries
Ensure that libraries are not explicitly titled. Dart provides automatic library titles, so avoid redundant naming of libraries in the code.
duplication-complexitystack-flutter+1
Low
DON'T make the parameter to == nullable
Ensure that parameters to `==` are non-nullable. Avoid using nullable parameters as they can introduce unexpected behavior and null reference errors.
error-handlingstack-flutter+1
Low
Dynamic import for heavy client-only widgets
Use next/dynamic with { ssr: false } for large client-only components (maps, editors) and provide a lightweight loading fallback.
stack-nextjsstack-react+2
Low
Element attribute order
Attributes within an element tag (including components) should be ordered consistently according to a predefined sequence (e.g., definitions, list rendering, conditionals, unique attributes, binding, events, content).
stack-vuestyle-conventions
Low
Element selectors with `scoped`
Avoid using element selectors (e.g., `button {... }`) directly within `<style scoped>`. Prefer class selectors.
performance-efficiencystack-vue+1
Low
Empty lines in component/instance options
Consider adding one empty line between multi-line properties (like complex `props`, `computed`, `methods`, `watch` objects) within the component options, especially in large components.
readability-refactorstack-vue+1
Low
Enable strict_types Mode for Type Checking
At the top of your PHP files (before any code), declare `declare(strict_types=1)`. This forces PHP to enforce the declared parameter and return types strictly, avoiding automatic type coercion.
stack-phpstyle-conventions
Low
Enable TS project references for depended packages
When a TS package depends on another workspace package, tsconfig.json must set "composite": true and include a "references" entry to the dependency; root must aggregate paths via tsconfig.base.json if used.
monorepo-hygienemaintainability+1
Low
Enforce Async/Await for asynchronous code
Check for the use of eval() to handle asynchronous execution. Eval leads to security vulnerabilities. Recommend using Async/Await or Promises instead.
error-handlingreadability-refactor+1
Low
Enhance logging with structured format
Prefer key-value or JSON logging over string concatenation; include correlation/request IDs from CoroutineContext when available.
observability-logging
Low
Ensure All Used Variables, Classes, and Functions Are Defined
Check for variables, functions, or classes that are used but not defined. This results in `NameError` and should be fixed by ensuring all symbols are properly declared.
error-handlingstack-python
Low
Ensure Consistent Attribute Placement
Check if attributes are consistently placed in the code, maintaining uniform formatting across the project.
style-conventions
Low
ETag/Last-Modified for non-immutable assets
For Go static servers, set immutable Cache-Control for hashed files; otherwise set "Cache-Control: no-cache" and support conditional GET via ETag or Last-Modified using file info.
web-static-assetscaching-strategy
Low
Export for portability in machine-readable format with consent check
Provide subject data export in JSONL or CSV only after confirming lawful basis (consent/contract). Include schema version and exclude internal linkage keys.
compliance-lgpdapi-conventions+1
Low
Extract business logic into separate methods
Move complex domain calculations out of controllers/handlers into services or private helpers.
module-architecturereadability-refactor
Low
Extract common parallel processing patterns
Encapsulate coroutine parallelization (map async/awaitAll, limited concurrency) into utilities.
concurrency-safetyduplication-complexity+1
Low
Extract common query logic
Factor repeated LINQ predicates/projections into reusable expressions or methods.