aif-architecture

Analyze project tech stack and context to generate ARCHITECTURE.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ichinya/idshka --skill aif-architecture-ichinya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-architecture
Source: https://github.com/ichinya/idshka/tree/main/.codex/skills/aif-architecture
Command: npx skills add https://github.com/ichinya/idshka --skill aif-architecture-ichinya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

An architecture guidance generator analyzes the project's tech stack and context to propose an architecture pattern and produce a concrete architecture document at a configurable path.

Core Features & Use Cases

  • Analyze the tech stack, project size, and domain to recommend an architecture pattern.
  • Generate the architecture artifact at .ai-factory/ARCHITECTURE.md with a structured, project-specific layout.
  • Integrate with project documentation to keep architecture decisions aligned with evolving requirements.

Quick Start

Describe your project context and run the aif-architecture skill to generate a tailored architecture document.

Frequently Asked Questions about aif-architecture

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

FAQPage Schema
How do I generate architecture guidelines for my project's tech stack?

To generate architecture guidelines, the skill reads your project configuration and DESCRIPTION.md, evaluates the tech stack and team size, and outputs a project-specific architecture document at .ai-factory/ARCHITECTURE.md with a structured layout tailored to your deployment needs.

What is the best way to decide an architecture pattern for a new software project?

The best way to decide an architecture pattern is to evaluate the project's tech stack, domain, and team size to generate a structured architecture document. This ensures the selected pattern aligns with deployment needs and integrates with existing project documentation.

Do I need a DESCRIPTION.md file to generate an architecture document?

Yes, a DESCRIPTION.md file is needed as the skill reads it to understand your project context. It combines this with configuration data to evaluate the domain and team size, ensuring the generated ARCHITECTURE.md aligns with your project's specific requirements.

Can I integrate architecture decisions with my existing project documentation?

Yes, architecture decisions integrate with existing project documentation by aligning related pointers and docs. The generated architecture artifact at .ai-factory/ARCHITECTURE.md keeps your architecture choices synchronized with evolving project requirements and technical context.

How does team size affect the recommended architecture pattern?

Team size affects the recommended architecture pattern by influencing the structural complexity documented in the generated ARCHITECTURE.md. The skill evaluates team size alongside deployment needs and tech stack to propose an architecture pattern that matches your project's operational scale.