jikime-domain-architecture

System design pattern selection depends on aligning your project scope, team capabilities, and non-functional requirements. This Skill guides you through evaluating options like a modular monolith versus microservices to ensure your architecture is scalable and maintainable.

Documenting architecture decisions is best achieved by creating Architecture Decision Records (ADRs). This Skill provides templates and guidance for capturing design rationale, ensuring critical architectural choices are recorded to reduce future architectural debt.

To structure your project directory for clean architecture, you should use best-practice directory layouts tailored to your chosen architectural style. This Skill offers templates that organize code logically to improve overall system maintainability.

Yes, this architecture design approach explicitly addresses small startup team capabilities and future scalability needs. It helps evaluate architectural patterns against your specific team size and SaaS project requirements to make informed decisions.

You should avoid microservices if your architecture does not align with your team capabilities or project scope. This Skill systematically addresses challenges in matching non-functional requirements, helping you decide when a simpler pattern is more appropriate.