skills.rest
lee-to
lee-toCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ai-factory.architecture

Guide architecture decisions for software projects using named patterns and decision criteria.

1.1k|92|Updated Feb 6, 2026
Search Tags:#design#architecture#microservices#domain-driven-design#decision-making#clean-architecture#system-design
One-click install
npx skills add https://github.com/lee-to/ai-factory --skill ai-factory-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-factory.architecture
Source: https://github.com/lee-to/ai-factory/tree/main/skills/architecture
Command: npx skills add https://github.com/lee-to/ai-factory --skill ai-factory-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are often ad-hoc and error-prone; this guide helps teams pick appropriate architectural patterns and make informed trade-offs.

Core Features & Use Cases

  • Guidance on pattern selection: Clean Architecture, DDD, microservices, modular monolith.
  • Decision framework: Clear criteria for choosing between architectures based on team size, domain complexity, deployment independence.
  • Use Case: For a new project, start with Modular Monolith and evolve to microservices as boundaries emerge.

Quick Start

Apply the guide to decide an architecture for your project and begin your design approach.

Frequently Asked Questions about ai-factory.architecture

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

FAQPage Schema
How do I choose between microservices and a modular monolith for my system design?▼

System design selection uses criteria like team size, domain complexity, and deployment independence. Start with a modular monolith for new projects and evolve to microservices as boundaries emerge.

How do I start applying domain-driven design to my software architecture?▼

Apply domain-driven design by following structured guidance and decision criteria to map domain complexity into your software architecture, using named patterns to enforce clear boundaries and inform refactoring plans.

What is the best way to structure a clean architecture refactoring plan?▼

The best way to structure a clean architecture refactoring plan is to use a decision framework that evaluates trade-offs, enforcing named patterns and clear criteria to guide the architectural review and implementation process.

Can I use this architecture guide for monolith refactoring plans?▼

Yes, the architecture guide applies directly to refactoring plans and architecture reviews across monoliths, modular monoliths, clean architecture, domain-driven design, and microservices.

When should I not use microservices for my software architecture?▼

Avoid microservices when team size is small or domain boundaries are unclear; the decision framework recommends starting with a modular monolith and evolving only as boundaries and deployment independence emerge.

Related Skills

Explore More Software Engineering Skills→
VoTruongDanhVoTruongDanh

architecture

architecture for your project.

Community
Advanced
openstatusHQopenstatusHQ
2.2k

improve-codebase-architecture

Identify architectural friction and generate RFCs for module-deepening refactors.

Official
Intermediate
angga30angga30

architect-review

Analyze system architecture to validate design decisions and assess risks.

Community
Advanced
xcrrrxcrrr
4

architecture-designer

Guide architecture pattern selection and document decisions with ADRs.

Community
Advanced