feature
Follows a strict 8-step workflow to implement PhotoManager features, ensuring architecture compliance and build integrity.
Install
mkdir -p .claude/skills/feature && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10473" && unzip -o skill.zip -d .claude/skills/feature && rm skill.zipInstalls to .claude/skills/feature
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Implement a new feature for PhotoManager following Clean Architecture workflow. Use this skill when asked to add new functionality, implement a user story, or add a new capability.Key capabilities
- →Implement features
- →Follow Clean Architecture
- →Check global usings
- →Run automated builds
How it works
It enforces a strict Clean Architecture workflow, requiring domain-first implementation and automated build/test verification.
Inputs & outputs
When to use feature
- →Implementing a new user story
- →Adding a database table to PhotoManager
- →Creating new service interfaces
- →Running feature builds and tests
About this skill
You are implementing a new feature for PhotoManager.
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 (inPhotoManager.Domain/UserConfigurationSettings/), or service interfaces are needed. -
Implement: Write code following Clean Architecture layer order:
- Domain first (entities, interfaces)
- Infrastructure (implementations)
- Application (orchestration)
- UI (ViewModels, Views) — only if needed
-
Using directives (NON-NEGOTIABLE):
- Check existing
GlobalUsings.csfiles in each project BEFORE adding anyusing - Only add a
usingif the namespace is NOT already in global usings - Unnecessary usings cause warnings and the project treats warnings as errors
- Check existing
-
Build: Run
dotnet build PhotoManager/PhotoManager.slnx— must produce zero warnings. -
Test: Write tests using NUnit + NSubstitute following conventions in
AGENTS.md. Run with:dotnet test --filter "FullyQualifiedName~ClassName" PhotoManager/PhotoManager.slnx -
Format: Run
dotnet format PhotoManager/PhotoManager.slnx --severity warn --verify-no-changes.
Return a summary of all changes made with file paths.
When not to use it
- →Adding unnecessary usings
- →Skipping tests
Prerequisites
Limitations
- →Warnings treated as errors
- →Strict layer order
How it compares
It mandates a specific order of operations and non-negotiable checks for global usings, preventing build warnings.
Compared to similar skills
feature side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| feature (this skill) | 0 | 2mo | No flags | Intermediate |
| csharp-pro | 9 | 4mo | No flags | Intermediate |
| dotnet-architect | 12 | 4mo | No flags | Advanced |
| component-development | 1 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
csharp-pro
sickn33
Write modern C# code with advanced features like records, pattern matching, and async/await. Optimizes .NET applications, implements enterprise patterns, and ensures comprehensive testing. Use PROACTIVELY for C# refactoring, performance optimization, or complex .NET solutions.
dotnet-architect
sickn33
Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns. Masters async/await, dependency injection, caching strategies, and performance optimization. Use PROACTIVELY for .NET API development, code review, or architecture decisions.
component-development
FritzAndFriends
Guidance for creating Blazor components that emulate ASP.NET Web Forms controls. Use this when implementing new components or extending existing ones in the BlazorWebFormsComponents library.
add-new-jit-ee-api
dotnet
Add a new API to the JIT-VM (aka JIT-EE) interface in the codebase.
try-fix
dotnet
Attempts ONE alternative fix for a bug, tests it empirically, and reports results. ALWAYS explores a DIFFERENT approach from existing PR fixes. Use when CI or an agent needs to try independent fix alternatives. Invoke with problem description, test command, target files, and optional hints.
functional-testing
MarkMichaelis
Generate and maintain functional / integration / E2E tests that validate user-facing behavior. Explore first, test second. Verify before claiming success. Language-aware: C#/xUnit, PowerShell/Pester, TypeScript/Playwright, and generic support.