Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
Refactor PhotoManager code following Clean Architecture patterns. Use this skill when asked to restructure, extract, move, or reorganize code while preserving behavior.
| name | feature |
| description | 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. |
| disable-model-invocation | true |
| argument-hint | <feature description> |
You are implementing a new feature for PhotoManager described as: $ARGUMENTS
Follow this workflow in order:
Understand: Read relevant existing code to understand patterns and conventions used in the affected layers.
Plan: Briefly outline the approach — which layers are affected, what new files/classes are needed, and what existing code must change.
Architecture: Determine if new database tables (in PhotoManager.Persistence/Sqlite/SqliteSchema.cs),
settings classes (in PhotoManager.Domain/UserConfigurationSettings/), or service interfaces are needed.
Implement: Write the code following Clean Architecture layer order:
Using directives (NON-NEGOTIABLE):
GlobalUsings.cs files in each project BEFORE adding any usingusing if the namespace is NOT already in global usingsBuild: Run dotnet build PhotoManager/PhotoManager.slnx and fix any errors or warnings.
The project has zero warnings — do not introduce any.
Test: Write comprehensive tests using NUnit + NSubstitute following the conventions in CLAUDE.md.
Run ONLY relevant tests: dotnet test --filter "FullyQualifiedName~ClassName" PhotoManager/PhotoManager.slnx
Format: Run dotnet format PhotoManager/PhotoManager.slnx --severity warn --verify-no-changes
to verify code style compliance.
Return a summary of all changes made with file paths.