aif-architecture

The skill evaluates team size, domain complexity, and scale requirements against a decision matrix. Small teams with simple domains fit Layered or Modular Monolith, while complex business logic suits Clean Architecture and large organizations with independent scaling needs fit Microservices.

Run the skill after creating a project DESCRIPTION.md, or provide project details manually. It reads your tech stack, recommends a pattern via an interactive question, then writes ARCHITECTURE.md with folder structures, dependency rules, and code examples in your language.

Yes, pass the pattern as an argument such as clean, ddd, microservices, monolith, or layers. The skill skips the recommendation step and generates the document for your chosen pattern directly.

Yes, all folder structures and code examples are adapted to the project's actual language and framework conventions, such as Next.js app directories or Go cmd layouts, rather than using generic TypeScript templates.

The skill warns that no project description was found and suggests running the setup skill first. You can still proceed by manually describing your project, tech stack, team size, and expected scale.

Avoid microservices with teams under ten people, unclear domain boundaries, or early-stage products seeking market fit. The operational complexity and slow initial velocity outweigh benefits; a Modular Monolith is usually the better starting point.