Free — no credit card
EZYE OS · AI Coding
Claude reads every file and still wrecks your architecture
One file fixes it — here are the 8 questions it must answer
The exact ARCHITECTURE.md template that stops Claude from guessing at decisions you made on purpose.
What's inside
- The 8 questions your ARCHITECTURE.md must answer
- Copy-paste structure with real examples for each
- The stop-and-ask rule that prevents silent boundary breaks
- When to use file tree vs ARCHITECTURE.md
EZYE OS · AI Coding Cheat Sheet
The ARCHITECTURE.md Playbook: 8 Questions That Make Claude Understand Your Codebase
by Divjot Sahni · EZYE Consulting · ezye.com.au
Why Claude misreads your codebase
1
Claude can already read every file — that was never the problem
2
What it can't do is guess the decisions that live in your head
3
An ARCHITECTURE.md is a map of intent, not a map of files
4
Without it, Claude "improves" a decision you made on purpose
Question 1 — What's in the system?
1
Write the map one level up from the code
2
Client → API → Services → Database
3
Keep it to the boxes that matter, not every module
4
This is the frame Claude reasons inside of...
Free access — enter your email below