ss-md-dotnet-architecture
Guide .NET architectural changes, especially when adding or moving classes, types, projects, modules, dependencies, services, or persistence boundaries. Use the relevant architecture guidance before proposing structural changes; do not impose layers on simple CRUD.
Pinned to revision 789e84f195a6, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/ss-md-dotnet-architecture/SKILL.md
- skills/ss-md-dotnet-architecture/references/anti-patterns.md
- skills/ss-md-dotnet-architecture/references/data-access.md
- skills/ss-md-dotnet-architecture/references/dependency-injection.md
- skills/ss-md-dotnet-architecture/references/events.md
- skills/ss-md-dotnet-architecture/references/file-organization.md
- skills/ss-md-dotnet-architecture/references/method-design.md
- skills/ss-md-dotnet-architecture/references/naming.md
- skills/ss-md-dotnet-architecture/references/orchestration.md
- skills/ss-md-dotnet-architecture/references/principles.md
- skills/ss-md-dotnet-architecture/references/project-structure.md
- skills/ss-md-dotnet-architecture/references/testing.md
- skills/ss-md-dotnet-architecture/references/type-boundaries.md
Every link opens the file at its source, pinned to the revision this page describes.