architect

Guide .NET solution architecture with Clean Architecture, DDD, and CQRS patterns.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/I-Synergy/CLAUDE.MD --skill architect-i-synergy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/I-Synergy/CLAUDE.MD/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/I-Synergy/CLAUDE.MD --skill architect-i-synergy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexities of designing scalable, maintainable, and secure software architectures, guiding users through technology selection and pattern implementation.

Core Features & Use Cases

  • Architecture Design: Provides guidance on Clean Architecture, DDD, microservices, and modular monoliths.
  • Technology Stack: Recommends specific technologies for .NET development, including databases, ORMs, and caching.
  • Use Case: A development team needs to design the architecture for a new enterprise application. They can use this Skill to define bounded contexts, choose appropriate patterns, and select a technology stack that aligns with project goals and existing infrastructure.

Quick Start

Use the architect skill to design the system architecture for a new e-commerce platform.

Frequently Asked Questions about architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design robust .NET system architecture for an enterprise application?

Designing .NET system architecture involves selecting architectural patterns like Clean Architecture, DDD, and CQRS, while enforcing adherence to project-specific technology guidelines and architectural decision-making processes for scalability and cross-cutting security.

What is the best way to implement Clean Architecture and DDD in a .NET application?

Implementing Clean Architecture and DDD requires structuring your .NET application into distinct layers, defining bounded contexts for domain models, and applying CQRS to separate read and write operations for maintainable, scalable software.

How do I select the right technology stack for a scalable .NET solution?

Selecting a scalable .NET technology stack involves evaluating specific technologies for databases, ORMs, and caching, while ensuring your choices align with architectural patterns and cross-cutting concerns like security and project-specific guidelines.

Can I use CQRS with a modular monolith architecture in .NET?

Yes, you can use CQRS with a modular monolith architecture in .NET. This combination allows you to separate command and query responsibilities within distinct bounded contexts, maintaining maintainability while preparing for potential future microservices extraction.

When should I choose a microservices architecture over a modular monolith for my system design?

Choosing between microservices and a modular monolith for system design depends on your scalability requirements and team structure; microservices offer independent deployment for complex domains, whereas modular monoliths provide simpler operational overhead for bounded contexts.

How do I handle cross-cutting concerns like security and scalability during system design?

Handling cross-cutting concerns like security and scalability during system design requires integrating architectural patterns that enforce consistent boundaries, ensuring your .NET application maintains robust performance and protection across all modules.