chore: add copilot code review instructions

Author: jvsena42

.github/copilot-instructions.md

@@ -0,0 +1,79 @@
+# GitHub Copilot Code Review Instructions
+
+When performing a code review, respond in English.
+
+## Architecture & Patterns
+
+When performing a code review, ensure ViewModels are never injected as dependencies into services or repositories. Only Android activities and composable functions should use ViewModels.
+
+When performing a code review, verify that all async operations use `viewModelScope.launch` instead of `GlobalScope.launch` in ViewModels.
+
+When performing a code review, ensure Repository pattern is followed with proper data source abstraction.
+
+When performing a code review, verify StateFlow is used for reactive state management in ViewModels with proper `_uiState` and `uiState` pattern.
+
+## Error Handling & Safety
+
+When performing a code review, flag any use of the not-null assertion operator (`!!`) and suggest safe calls (`?.`) with proper null handling.
+
+When performing a code review, ensure all coroutine operations use proper error handling with `runCatching`
+
+When performing a code review, verify that all Logger calls include the TAG as context parameter, e.g., `Logger.warn("message", e = e, context = TAG)`.
+
+When performing a code review, check that methods exist before they are called, especially after refactoring.
+
+## UI & Compose Best Practices
+
+When performing a code review, ensure all user-facing strings use `stringResource(R.string.*)` instead of hardcoded strings.
+
+When performing a code review, verify that expensive Compose computations are wrapped in `remember` blocks.
+
+When performing a code review, check that Material3 design guidelines are followed for UI components.
+
+When performing a code review, ensure proper state management patterns with `MutableStateFlow` and `StateFlow`.
+
+## Code Quality & Readability
+
+When performing a code review, focus on readability and avoid nested ternary operators.
+
+When performing a code review, ensure unused code is removed after refactoring.
+
+When performing a code review, verify that existing extensions and utilities are used rather than creating duplicate functionality.
+
+## Dependency Injection & Services
+
+When performing a code review, verify proper Hilt dependency injection patterns are followed.
+
+When performing a code review, ensure services contain business logic and don't directly depend on ViewModels.
+
+## Build & Testing
+
+When performing a code review, ensure proper build variant usage (dev for regtest, tnet for testnet).
+
+When performing a code review, verify that unit tests follow the pattern `./gradlew testDevDebugUnitTest --tests ClassName`.
+
+When performing a code review, suggest Unit Test com composable components and business logic covering the most important cases
+
+## Lightning & Bitcoin Specific
+
+When performing a code review, ensure proper usage of LDK Node and bitkitcore library patterns.
+
+When performing a code review, verify that Bitcoin/Lightning operations are properly handled in the service layer.
+
+When performing a code review, verify that propper Bitcoin and Lightning technical terms are used when naming code components
+
+## Performance & Memory
+
+When performing a code review, check for potential memory leaks in coroutines and ensure proper scope usage.
+
+When performing a code review, verify that database operations use Room patterns correctly.
+
+When performing a code review, ensure network operations use Ktor patterns and proper error handling.
+
+## Documentation & Maintenance
+
+When performing a code review, ensure code follows the established patterns from the existing codebase.
+
+When performing a code review, verify that complex business logic is properly documented.
+
+When performing a code review, check that new features integrate well with the existing MVVM architecture.