/solid-csharp
Use when writing or refactoring C#/.NET code, structuring Modules/[Feature]/ layers, or defining Contracts/ interfaces (SOLID, files < 100 lines).
$ npx -y skills add fusengine/agents --skill solid-csharp --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/solid-csharp
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when writing or refactoring C#/.NET code, structuring Modules/[Feature]/ layers, or defining Contracts/ interfaces (SOLID, files < 100 lines).
SKILL.md
solid-csharp.SKILL.mdname: solid-csharp
description: "Use when writing or refactoring C#/.NET code, structuring Modules/[Feature]/ layers, or defining Contracts/ interfaces (SOLID, files < 100 lines)."
versions:
csharp: "12"
dotnet: "9"
user-invocable: true
references: references/principles.md, references/patterns.md
related-skills: solid-detection
<objective> SOLID C# enforces a modular architecture for C# 12/.NET 9 projects: every feature lives under `Modules/[Feature]/` (Controllers, Services, Repositories, Contracts, Models) with shared code centralized in `Core/`, contracts are mandatory and live only in `Contracts/` directories, and interfaces stay small (1-3 members). File limits are strict (100 lines, split at 90; controllers under 50).
Before writing any new code it requires a DRY check -- grep the codebase and `Core/Services`/`Core/Contracts` for existing logic to reuse before creating something new. See `principles.md` for the 5 SOLID principles and `patterns.md` for directory layout, testing, and record usage. </objective>
SOLID C# - Modular Architecture
Agent Workflow (MANDATORY)
Before ANY implementation, use `TeamCreate` to spawn 3 agents:
1. **fuse-ai-pilot:explore-codebase** - Analyze existing architecture 2. **fuse-ai-pilot:research-expert** - Verify .NET docs via Context7 3. **fuse-ai-pilot:sniper** - Post-implementation validation
---
DRY - Reuse Before Creating (MANDATORY)
**Before writing ANY new code:** 1. **Grep the codebase** for similar interfaces, services, or logic 2. Check shared locations: `Core/Services/`, `Core/Contracts/` 3. If similar code exists -> extend/reuse instead of duplicate 4. If code will be used by 2+ features -> create it in `Core/`
---
Architecture (Modules MANDATORY)
| Layer | Location | Max Lines | |-------|----------|-----------| | Controllers | `Modules/[Feature]/Controllers/` | 50 | | Services | `Modules/[Feature]/Services/` | 100 | | Repositories | `Modules/[Feature]/Repositories/` | 100 | | Contracts | `Modules/[Feature]/Contracts/` | 30 | | Models | `Modules/[Feature]/Models/` | 50 | | Shared | `Core/{Services,Contracts,Models}/` | - |
**NEVER use flat structure - always `Modules/[Feature]/`**
---
Critical Rules (MANDATORY)
| Rule | Value | |------|-------| | File limit | 100 lines (split at 90) | | Controllers | < 50 lines, delegate to services | | Interfaces | `Contracts/` directory ONLY | | XML docs | Every public member documented | | DI | Use `Microsoft.Extensions.DependencyInjection` | | Small interfaces | 1-3 members max | | Records | Prefer `record` for DTOs and value objects |
---
Reference Guide
| Topic | Reference | When to consult | |-------|-----------|-----------------| | **SOLID Principles** | [principles.md](references/principles.md) | Quick reference for all 5 principles | | **Patterns & Structure** | [patterns.md](references/patterns.md) | Directory layout, testing, records |
---
Forbidden
| Anti-Pattern | Fix | |--------------|-----| | Files > 100 lines | Split at 90 | | Interfaces in impl files | Move to `Contracts/` directory | | Fat interfaces (4+ members) | Split into focused interfaces | | Flat project structure | Use `Modules/[Feature]/` | | `new` for dependencies | Use constructor injection + DI | | Service Locator pattern | Use constructor injection |
Read more
name: solid-csharp description: "Use when writing or refactoring C#/.NET code, structuring Modules/[Feature]/ layers, or defining Contracts/ interfaces (SOLID, files < 100 lines)." versions: csharp: "12" dotnet: "9" user-invocable: true references: references/principles.md, references/patterns.md related-skills: solid-detection
<objective> SOLID C# enforces a modular architecture for C# 12/.NET 9 projects: every feature lives under `Modules/[Feature]/` (Controllers, Services, Repositories, Contracts, Models) with shared code centralized in `Core/`, contracts are mandatory and live only in `Contracts/` directories, and interfaces stay small (1-3 members). File limits are strict (100 lines, split at 90; controllers under 50).
Before writing any new code it requires a DRY check -- grep the codebase and `Core/Services`/`Core/Contracts` for existing logic to reuse before creating something new. See `principles.md` for the 5 SOLID principles and `patterns.md` for directory layout, testing, and record usage. </objective>
SOLID C# - Modular Architecture
Agent Workflow (MANDATORY)
Before ANY implementation, use `TeamCreate` to spawn 3 agents:
1. **fuse-ai-pilot:explore-codebase** - Analyze existing architecture 2. **fuse-ai-pilot:research-expert** - Verify .NET docs via Context7 3. **fuse-ai-pilot:sniper** - Post-implementation validation
---
DRY - Reuse Before Creating (MANDATORY)
**Before writing ANY new code:** 1. **Grep the codebase** for similar interfaces, services, or logic 2. Check shared locations: `Core/Services/`, `Core/Contracts/` 3. If similar code exists -> extend/reuse instead of duplicate 4. If code will be used by 2+ features -> create it in `Core/`
---
Architecture (Modules MANDATORY)
| Layer | Location | Max Lines | |-------|----------|-----------| | Controllers | `Modules/[Feature]/Controllers/` | 50 | | Services | `Modules/[Feature]/Services/` | 100 | | Repositories | `Modules/[Feature]/Repositories/` | 100 | | Contracts | `Modules/[Feature]/Contracts/` | 30 | | Models | `Modules/[Feature]/Models/` | 50 | | Shared | `Core/{Services,Contracts,Models}/` | - |
**NEVER use flat structure - always `Modules/[Feature]/`**
---
Critical Rules (MANDATORY)
| Rule | Value | |------|-------| | File limit | 100 lines (split at 90) | | Controllers | < 50 lines, delegate to services | | Interfaces | `Contracts/` directory ONLY | | XML docs | Every public member documented | | DI | Use `Microsoft.Extensions.DependencyInjection` | | Small interfaces | 1-3 members max | | Records | Prefer `record` for DTOs and value objects |
---
Reference Guide
| Topic | Reference | When to consult | |-------|-----------|-----------------| | **SOLID Principles** | [principles.md](references/principles.md) | Quick reference for all 5 principles | | **Patterns & Structure** | [patterns.md](references/patterns.md) | Directory layout, testing, records |
---
Forbidden
| Anti-Pattern | Fix | |--------------|-----| | Files > 100 lines | Split at 90 | | Interfaces in impl files | Move to `Contracts/` directory | | Fat interfaces (4+ members) | Split into focused interfaces | | Flat project structure | Use `Modules/[Feature]/` | | `new` for dependencies | Use constructor injection + DI | | Service Locator pattern | Use constructor injection |
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill

