Codebase Architecture Mapper FAQs

Question 1

Does this skill suggest improvements to my code?

Accepted Answer

No, it is designed to be a documentarian rather than an evaluator. it records exactly what exists in the codebase without offering subjective suggestions or refactoring advice.

Question 2

Where are the architecture snapshots stored?

Accepted Answer

The snapshots are saved as Markdown files in the 'memory/' directory, following a naming convention that includes a timestamp and a descriptive claim for easy retrieval.

Question 3

Can I limit the scope of the architecture mapping?

Accepted Answer

Yes, the command accepts an optional scope argument such as a specific directory path or module name, allowing you to document specific parts of a system instead of the full codebase.

Question 4

How does this help with AI-assisted development?

Accepted Answer

By creating a 'source of truth' for the project structure, it ensures Claude has the correct architectural context, which leads to more accurate code generation and better understanding of project-specific patterns.

Question 5

What does the /eidos:architecture command do?

Accepted Answer

It generates a detailed Markdown snapshot of your current codebase structure, tech stack, and architectural patterns to serve as a reference for both human developers and the AI.

Codebase Architecture Mapper

主要功能

使用场景

Codebase Architecture Mapper

主要功能

使用场景