aif-architecture

To generate architecture guidelines, analyze the project's tech stack and context to assess scale, team size, and domain complexity. This produces a tailored architecture pattern and an actionable .ai-factory/ARCHITECTURE.md file containing folder layout, dependency rules, and implementation guidance.

Choosing an architecture pattern involves evaluating your project's specific tech stack, domain complexity, and team size. The process selects an appropriate pattern by assessing these contextual factors and documenting the rationale, structure, and dependency directions in a comprehensive markdown file.

Creating folder layout and dependency direction rules requires analyzing your project context and deployment needs. The output is a structured ARCHITECTURE.md document that defines actionable rules, folder structures, and implementation guidance ready for direct integration into your codebase.

Yes, architecture documentation can be tailored by assessing your team size and domain complexity. The system provides project-aware guidance that generates rationale, structural rules, and implementation guidance reflecting your specific scale and deployment requirements.

Architecture guidelines for faster onboarding should include a recommended architecture pattern, rationale, folder structure, dependency rules, and implementation guidance. These actionable rules reflect the current tech stack and project context to enable consistent development decisions.