TermRemoteCtl/AGENTS.md

30 lines
1.2 KiB
Markdown

# AGENTS.md
## Tooling
- Flutter SDK path: `C:\tools\flutter\bin\flutter.bat`
- On Windows, use the absolute Flutter path instead of relying on `PATH`.
- Prefer running Flutter and Dart work from the repository root or the app directory with the absolute Flutter path.
## Windows Shell Setup
- Before running commands, initialize the terminal as UTF-8:
- `chcp 65001`
- `[Console]::InputEncoding = [System.Text.UTF8Encoding]::new($false)`
- `[Console]::OutputEncoding = [System.Text.UTF8Encoding]::new($false)`
- `$OutputEncoding = [System.Text.UTF8Encoding]::new($false)`
- `$env:PYTHONUTF8 = '1'`
- `$env:PYTHONIOENCODING = 'utf-8'`
## Common Commands
- Run all mobile app tests:
- `C:\tools\flutter\bin\flutter.bat test`
- Run a targeted Flutter test:
- `C:\tools\flutter\bin\flutter.bat test test/widget_test.dart`
- Run Windows agent tests:
- `dotnet test apps/windows_agent/TermRemoteCtl.Agent.sln`
## Encoding Rules
- All source, config, Markdown, JSON, YAML, TOML, and script files must use UTF-8 without BOM.
- Do not rely on terminal rendering alone to diagnose encoding issues.
- Always read and write text files explicitly as UTF-8 when tooling requires an encoding choice.