Keep implementation choices tied to the project.
1. Inspect before edit
Let the workflow examine current APIs and patterns before changing code. Similar projects may require different migration details.
2. Diff review
Read the complete diff, including generated configuration and dependency changes. Reject unrelated edits and verify that suggested abstractions fit the repository.
3. Incremental checks
Run the smallest meaningful validation after each coherent change. A full build at the end is useful but gives less precise feedback when many unrelated changes are mixed.
Worked scenario
A UI skill changes both insets and navigation architecture. Only the inset change belongs to the task unless the architecture change is necessary and justified.
Apply it
Apply a small skill-guided improvement and annotate why each changed file is required.
Check your understanding
Every modified file has a clear relationship to the requested outcome. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.