Guides software architecture design using Domain-Driven Design, Clean Architecture, and SOLID principles.
npx skills add https://github.com/victorzhuk/go-ent --skill arch-core
Please help me install this Agent Skill. Skill: arch-core Source: https://github.com/victorzhuk/go-ent/tree/main/pkg/skills/core/arch-core Command: npx skills add https://github.com/victorzhuk/go-ent --skill arch-core
This Skill provides expert guidance on designing robust, maintainable, and scalable software architectures, focusing on Clean Architecture, Domain-Driven Design, and SOLID principles.
Provide architecture diagrams for a layered e-commerce application.
High-intent search queries and answers about installing and using this skill.
To design layered architecture, enforce clear dependency rules and separation of concerns using Clean Architecture and SOLID principles. This ensures maintainable system boundaries and a robust structure for your application's data flow.
Defining bounded contexts requires Domain-Driven Design to establish clear domain boundaries and responsibilities. This approach ensures scalable microservices by enforcing strict separation of concerns and maintainable system boundaries.
Document architectural decisions by creating Architectural Decision Records (ADRs). This process captures the rationale behind selected design patterns and structural choices, ensuring maintainable and transparent software architecture documentation.
Yes, you can generate architecture diagrams that visualize system structure, layers, and data flow. These diagrams facilitate the creation of clear package layouts reflecting your architectural boundaries and dependency rules.
You should reconsider Clean Architecture if your project lacks complexity or does not require strict separation of concerns. Over-implementing layered architecture and bounded contexts on simple systems introduces unnecessary structural overhead.
Selecting design patterns involves evaluating your system boundaries and applying SOLID principles. This ensures the chosen patterns align with your Domain-Driven Design strategy and maintainable architecture requirements.
cameronraysmithReverse engineer an Event Model from a brownfield codebase into EventCatalog-ready documentation.
xiongxianfeiOrganize durable architectural decisions and system design context across components.
jabrenaGenerate PlantUML diagrams for Java project architecture.
mwathibenImplement CQRS with separate command and query handlers for event-sourced systems.
