aif-architecture

To generate architecture guidelines, provide your project's tech stack in a DESCRIPTION.md file. The skill analyzes the stack to recommend an architecture pattern and creates an ARCHITECTURE.md document with actionable setup rules.

Choosing an architecture pattern is handled by analyzing your tech stack from DESCRIPTION.md. The system evaluates the stack and recommends a suitable pattern like Clean Architecture, DDD, Modular Monolith, or Layered, then documents the design decisions.

Yes, you can use this to document design decisions for a major project refactor. It applies during major refactors by evaluating your current tech stack and generating a structured ARCHITECTURE.md file with clear rules for dependencies and module communication.

You need to provide a DESCRIPTION.md file containing your project context and tech stack. The system uses this input to produce a tailored .ai-factory/ARCHITECTURE.md file containing the recommended pattern and key architectural principles.

The system structures module communication and dependency rules by applying a practical decision flow based on your tech stack. It outputs clear guidelines within the generated ARCHITECTURE.md document to enforce structured dependencies and key principles.

You should avoid automating architecture decisioning if your project lacks a defined tech stack in DESCRIPTION.md. Without this input, the system cannot accurately analyze the stack or recommend a suitable architecture pattern and dependency rules.