project-architecturelisted

# Project Architecture Guide ## Purpose Capture the specific architectural decisions, design taste, and coding conventions for each project. Instead of Claude guessing how to structure code, it reads the project's established patterns and follows them exactly. This follows Anthropic's practice: don't explain basic programming to Claude - instead invest the text in explaining your project's specific quirks and the exact design taste you prefer. ## How It Works ### Setting Up for a New Project When starting a new project or first working on an existing one: 1. Create `examples/{project-name}.md` in this directory 2. Analyze the existing codebase (if any) to detect patterns 3. Ask the user about their preferences for: - File/folder structure - Naming conventions - State management approach - Styling approach (CSS modules, Tailwind, styled-components) - Testing strategy - Error handling patterns - API communication patterns - Hebrew/RTL handling (if applicable) 4. Document everything with CODE EXAMPLES, not just descriptions ### Using the Architecture Guide Before writing any significant code: 1. Check if `examples/{project-name}.md` exists 2. If yes, read it and follow its patterns EXACTLY 3. If patterns conflict with what Claude would normally do - the guide wins 4. If encountering a new situation not covered - ask the user, then add to guide ## Architecture File Format File: `examples/{project-name}.md` ```markdown # {Project Name} Architectur