aif-architecture

Generate tailored ARCHITECTURE.md guidelines from project tech stack and context.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ExsyDev/eye-blinking --skill aif-architecture-exsydev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-architecture
Source: https://github.com/ExsyDev/eye-blinking/tree/main/.claude/skills/aif-architecture
Command: npx skills add https://github.com/ExsyDev/eye-blinking --skill aif-architecture-exsydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates architecture guidelines tailored to a project's context by analyzing tech stack and existing constraints.

Core Features & Use Cases

  • Load project context from .ai-factory/DESCRIPTION.md and optional skill-context rules to customize architecture decisions.
  • Produce a detailed ARCHITECTURE.md document and place it under .ai-factory/ARCHITECTURE.md with rationale, structure, and rules.
  • Optional: update project DESCRIPTION and AGENTS as needed.

Quick Start

Describe your project context and request an architecture guideline to generate a tailored ARCHITECTURE.md.

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 tailored to my project's tech stack?

To generate architecture guidelines, describe your project context and tech stack so the tool can analyze constraints and produce a tailored ARCHITECTURE.md document with rationale and structure.

What is an architecture doc and why do I need one for my software project?

An architecture doc defines your project's structure, decisions, and rules. You need one to ensure architecture decisions respect project conventions and provide clear rationale for future development.

How do I create an ARCHITECTURE.md file that respects existing project conventions?

Creating an ARCHITECTURE.md that respects conventions requires loading project context from DESCRIPTION.md and optional skill-context rules, then applying analyzed tech stack constraints to generate tailored guidelines.

Can I customize architecture decisions based on my existing project context?

Yes, you can customize architecture decisions by providing project context. The tool loads existing constraints from DESCRIPTION.md and skill-context rules to tailor the generated architecture guidelines accordingly.

What's the best way to document software architecture rationale and structure?

The best way to document architecture rationale is generating a tailored ARCHITECTURE.md file. This approach analyzes your tech stack and produces documentation including both the structural decisions and their underlying rationale.

Do I need a DESCRIPTION.md file before generating architecture guidelines?

Yes, a DESCRIPTION.md file under .ai-factory is needed to load project context. The architecture generation process reads this file to analyze tech stack and constraints for tailoring decisions.