architecture

Evaluate and improve system design across architectural layers with best practices.

8|13|Updated Apr 13, 2026

Search Tags:#architecture #refactoring #design-patterns #api-design #system-design #database-design

Ready to run

npx skills add https://github.com/queen-of-code/AI-DLC --skill architecture-queen-of-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/queen-of-code/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/architecture
Command: npx skills add https://github.com/queen-of-code/AI-DLC --skill architecture-queen-of-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces uncertainty and costly rework by providing clear architectural guidance for designing, refactoring, and reviewing software systems so teams can make consistent, well-reasoned decisions.

Core Features & Use Cases

Principled Guidance: Explains SOLID, separation of concerns, and layering to improve maintainability and testability.
Pattern Recommendations: Advises on dependency injection, repository and service layers, event-driven designs, and caching strategies.
Decision Frameworks: Helps choose monolith vs microservices, design REST/GraphQL APIs, and decide normalization and indexing strategies for databases.
Use Case: Conduct an architecture review of a backend service to identify god classes, coupling issues, and a prioritized refactor plan.

Quick Start

Ask the architecture skill to review the repository structure and provide a layered architecture recommendation with identified violations and concrete refactoring steps.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I evaluate my system design for separation of concerns and SOLID principles?▼

Evaluating system design involves applying software architecture best practices across presentation, application, domain, and infrastructure layers to identify violations of SOLID principles and separation of concerns, providing concrete refactoring steps to improve maintainability.

What's the best way to choose between a monolith and microservices architecture?▼

Choosing between monolith and microservices requires applying architectural decision frameworks that document trade-offs, evaluating system requirements for event-driven designs and caching strategies, and recommending the most appropriate structural pattern for your specific scale and complexity.

How do I conduct an architectural review of a backend service to identify coupling issues?▼

Conducting an architectural review involves analyzing the repository structure to detect god classes and coupling issues across layered architecture, generating a prioritized refactor plan with recommended actions to resolve identified design violations and improve system maintainability.

When do I need event-driven patterns and caching strategies in my software architecture?▼

Event-driven patterns and caching strategies are needed when designing new systems that require scalable communication between services and optimized data retrieval, ensuring the architecture meets specific performance requirements while documenting the associated trade-offs.

How do I design REST and GraphQL APIs with proper database normalization and indexing?▼

Designing REST and GraphQL APIs involves applying architectural best practices to decide normalization and indexing strategies for databases, ensuring the API design aligns with domain layer requirements and supports efficient data access patterns across the system.

Can I use design patterns like dependency injection and repository layers to refactor my codebase?▼

Yes, using design patterns like dependency injection, repository layers, and service layers is recommended during codebase refactoring to reduce uncertainty and costly rework, providing well-reasoned structural improvements that enhance testability and maintainability.