Claude.md Architecture Manager FAQs

Question 1

When is it appropriate to create a subdirectory CLAUDE.md?

Accepted Answer

Create one when a domain has non-obvious contracts with other parts of the system, when invariants exist that aren't obvious from the code, or when architectural decisions affect how that specific code should evolve.

Question 2

How do I ensure the date in my CLAUDE.md isn't hallucinated?

Accepted Answer

This skill mandates using the Bash command `date +%Y-%m-%d` to fetch the actual system date before writing or updating the file.

Question 3

Should I use @ references to link files in my CLAUDE.md?

Accepted Answer

No. Using the @ syntax force-loads those files into the context window, which wastes tokens. Simply naming the files allows Claude to find and read them only when they are relevant to the task at hand.

Question 4

What is the difference between a top-level and domain-level CLAUDE.md?

Accepted Answer

Top-level files focus on the 'How' of a project (build commands, tech stack, general conventions), while domain-level files focus on the 'Why' (architectural intent, public contracts, and invariants).

Question 5

Why is the freshness date mandatory in CLAUDE.md?

Accepted Answer

Stale documentation is often misleading. The 'Last verified' date signals exactly when the architectural contracts were last confirmed by a developer, preventing the AI from relying on outdated information.

Claude.md Architecture Manager

Claude.md Architecture Manager

Key Features

Use Cases

Key Features

Use Cases