Code Quality

Ship a lean machine-targeted instruction file at the repo root that states build/test/run commands, conventions, and what is out of scope.

Characterize the computational profile of each candidate scope group by identifying dominant algorithms, data structures, and complexity characteristics.

Characterize how components communicate within the application — delegation, pub/sub, shared state, and other in-process coordination patterns.

Use MVVM with [CommunityToolkit.Mvvm](https://learn.microsoft.com/en-us/dotnet/communitytoolkit/mvvm/) — source-gener...

Pick a .NET target framework from the documented support cadence: LTS for apps, multi-target libraries, pin the SDK.

Decide a Windows UI framework and deployment model deliberately and early; package identity is mandatory for notifications and background tasks.

Distinguish concerns that span all scope groups (cross-cutting — do not isolate) from shared infrastructure that is itself a coherent group.

Identify scope groups by measuring internal coupling density versus external coupling — files that import each other heavily belong together.

Separate the irreducible complexity of the problem from incidental complexity, then spend agents on the incidental and design review on the essential.

Identify the architectural patterns imposed by the chosen framework and use those conventional units as primary scope group candidates.

Group files by their shared public API surface — types, protocols, and exported symbols that define a coherent contract.

Share domain and data logic broadly across platforms with KMP; choose shared vs native UI per platform maturity.

Identify scope group boundaries by finding groups of objects that are created, owned, and destroyed together as a unit.

Identify scope group candidates by locating explicit build targets, package manifests, and declared module boundaries.

Classify every file by its primary reason for existing, and verify that each candidate scope group has a single coherent purpose.

Identify permissions, entitlements, environment checks, and configuration prerequisites that constrain when and where code can execute.

Only modify what was requested. State the goal before starting. Note but do not fix adjacent issues.

Before writing new code, check the platform, your existing dependencies, your own codebases, and proven open source — and verify any candidate dependency is real.

For non-trivial agent work, write a self-contained spec before code, separating planning from execution and ending with a verification step.

Characterize which external libraries, OS frameworks, and system services the code reaches for, and what that implies about scope boundaries.

Characterize how the code communicates with the operating system — IPC, lifecycle callbacks, background execution, and OS-level integration points.