dev-conventionslisted

# Development Conventions General rules that apply across all projects. Read and follow before making any code change. ## Reuse Before Creating - Before adding a component, helper, constant, service, or utility: search the codebase first - If an equivalent already exists, import and reuse it - Extend existing components with props or small local composition before creating variants - Only add a helper, service, or shared constant when logic is reused across files or clearly belongs to an existing shared module - If logic is local to one screen or form, keep it as a private local helper: do not extract prematurely ## No Duplication - Shared business logic belongs in the project's shared service or domain layer - Shared UI belongs in the project's shared widget or component layer - Shared constants belong in the relevant domain file: not scattered per file - Do not create a variant of something that already exists: parameterize or extend instead ## Scope Control - Make the requested change at the layer where it belongs - Do not update downstream consumers, exports, reports, or unrelated screens unless the request explicitly requires it - Do not refactor surrounding code while fixing a targeted issue ## Localization - All user-facing strings must go through the project's i18n / localization system - Never hardcode visible text in source code - Add or update keys in all supported language files simultaneously - Do not localize outputs that have a fixed statutory or legal