Free — no credit card
EZYE OS · AI Coding
Claude reads every file in your repo
and still guesses your architecture wrong
The 8 questions your ARCHITECTURE.md must answer so Claude stops rewriting decisions you made on purpose.
What's inside
- The 8-question ARCHITECTURE.md framework in full
- Exact examples for boundaries, ownership and data flow
- A stop-and-ask rule that halts silent breakages
- A copy-ready template to steal for your repo
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 the file tree isn't enough
1
Claude can already read every file in your repo
2
What it can't read is the decisions that were never written down
3
An ARCHITECTURE.md maps intent, not files
4
Skip it and Claude 'improves' choices you made deliberately
Question 1 — What's in the system?
1
Draw 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 orientation layer before any rule applies
Free access — enter your email below