القائمة
Refactor PhotoManager code following Clean Architecture patterns. Use this skill when asked to restructure, extract, move, or reorganize code while preserving behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Add or modify tests following project conventions. Use when asked to write tests, add test coverage, or fix failing tests.
Add or modify tests for PhotoManager following project conventions. Use this skill when asked to write tests, add test coverage, or fix failing tests.
Avalonia UI reference guide for PhotoManager: UI conventions, MVVM patterns, and cross-platform UI patterns. Use this skill when working on UI code, adding image-processing methods, or needing to understand the Avalonia UI layer of the application.
Refactor code following Clean Architecture patterns. Use when asked to restructure, extract, move, or reorganize code while preserving behavior.
Avalonia UI reference guide for PhotoManager: UI conventions, MVVM patterns, and cross-platform UI patterns. Use this skill when working on UI code, adding image-processing methods, or needing to understand the Avalonia UI layer of the application.
Implement a new feature for PhotoManager with full workflow. Use when asked to add new functionality, implement a user story, or add a new capability.
استنادا إلى تصنيف SOC المهني
| name | refactor |
| description | Refactor PhotoManager code following Clean Architecture patterns. Use this skill when asked to restructure, extract, move, or reorganize code while preserving behavior. |
You are refactoring PhotoManager code. Preserve all existing behavior.
Follow this workflow in order:
Understand: Read all code involved. Map dependencies across layers (UI → Application → Domain ← Infrastructure ← Persistence).
Verify coverage: Before changing anything, check that tests exist for the code being refactored. Write missing tests first to lock in current behavior.
Plan: Identify changes needed while respecting Clean Architecture boundaries. Domain must NOT depend on Infrastructure or UI.
Apply changes incrementally: After each change:
dotnet build PhotoManager/PhotoManager.slnx — verify zero warningsCheck GlobalUsings.cs before adding any using directives.
Update DI registration in {Layer}ServiceCollectionExtensions.cs if services move or rename.
Verify the chain in App.axaml.cs: AddInfrastructure() → AddDomain() → AddApplication() → AddUi()
Final verification:
dotnet build PhotoManager/PhotoManager.slnx — zero warningsdotnet test --filter "FullyQualifiedName~AffectedClass" PhotoManager/PhotoManager.slnxdotnet format PhotoManager/PhotoManager.slnx --severity warn --verify-no-changes