rm-guide-architecture

Design clean C# service boundaries by keeping abstractions small and explicit, ensuring dependencies flow inward, and separating domain, application, infrastructure, and presentation concerns to prevent brittle systems. Each type should have a single reason to change.

Prefer composition over inheritance in C# architecture to limit dependency flows and ensure each type has one reason to change. This pattern discipline prevents unnecessary architectural complexity and keeps service contracts clear during cross-layer refactors.

Structure cross-layer C# refactors by aligning architecture decisions around inward dependencies and single-responsibility clarity. Keep domain, application, infrastructure, and presentation concerns separate to prevent unnecessary architectural complexity and maintain clear contracts.

Apply architectural guardrails when planning a new C# feature slice or refactoring service boundaries. Consult principles for composition, inward dependency flow, and single-responsibility checks to prevent unnecessary complexity and keep abstractions explicit.

Yes, this architecture guidance explicitly separates domain, application, infrastructure, and presentation concerns in C# services. It ensures dependencies flow inward and abstractions remain small and explicit, keeping boundaries clear during cross-layer changes.

Keep abstractions small and explicit in C# services by applying pattern discipline that encourages composition over inheritance. Ensure dependencies flow inward and each type has a single reason to change, preventing unnecessary architectural complexity.