The single ARCHITECTURE.md file that answers six questions so Claude stops guessing and starts building the way you intended.
What's inside
by Divjot Sahni · EZYE Consulting · ezye.com.au
Why context isn't understanding
Claude reads every file in your repo but nobody told it WHY the code is organized the way it is
Reading code shows the what; it never shows the intent behind the structure
This is why Claude 'fixes' things that were never broken and drifts from your patterns
The fix isn't more context. It's one documentation file that encodes your decisions
The 6 questions (preview)
Question 1: What is this system and who uses it?
Question 2: What are the major components and how do they talk to each other?
Questions 3 through 6 cover data flow, conventions, boundaries, and the rules Claude must never break...
Free access — enter your email below