Guide software architecture decisions across patterns, trade-offs, and documentation.
npx skills add https://github.com/lushly-dev/afd --skill architect-systems
Please help me install this Agent Skill. Skill: architect-systems Source: https://github.com/lushly-dev/afd/tree/main/.claude/skills/architect-systems Command: npx skills add https://github.com/lushly-dev/afd --skill architect-systems
This Skill addresses the complexity of designing scalable, maintainable software systems by providing guidance on architectural patterns, decision-making frameworks, and best practices for agent-assisted development.
Use the architect-systems skill to help choose between a monolith and microservices for a new e-commerce platform.
High-intent search queries and answers about installing and using this skill.
System design pattern selection involves evaluating trade-offs between monoliths and microservices based on your scalability and maintainability requirements. This Skill guides architectural pattern choices by comparing modular monoliths, event-driven architectures, and microservices to help you determine the right fit for your project context.
Domain decomposition using DDD bounded contexts requires identifying core domain boundaries and mapping them to autonomous service limits. This Skill applies Domain-Driven Design principles to help you define bounded contexts, evaluate dependencies, and plan evolutionary architecture migrations effectively.
Writing an Architecture Decision Record (ADR) involves documenting your architectural decisions, the context surrounding them, and the evaluated trade-offs. This Skill facilitates ADR authoring to capture key choices like adopting CQRS or hexagonal architecture, ensuring design rationale is transparent and maintainable.
Platform engineering principles can structure agent-maintainable architecture by creating standardized interfaces and modular boundaries. This Skill promotes designing systems so AI agents can easily understand, modify, and extend codebases by applying ports-and-adapters patterns and fitness functions for evolutionary architecture.
You should avoid event-driven architecture or CQRS when system complexity does not justify the operational overhead of eventual consistency and message routing. This Skill helps evaluate architectural trade-offs, ensuring you only adopt complex patterns like CQRS when scaling demands require them.
EnigmaWUDefine bounded contexts and map integration contracts for domain-driven design.
johangm90Design software architecture with bounded contexts, vertical slices, ADRs, and PRDs.
NovaAI-innovationAutomate CI/CD pipeline setup, Terraform infrastructure provisioning, and application deployment.
Prathmesh2000Decompose complex software domains into bounded contexts using DDD patterns.
