rsrini7 · April 22, 2025 02:46
diff --git a/claude-improved b/claude-improved
 I need you to analyze this codebase as an expert software architect. Please provide:

 ### Project Overview
 - Core purpose and value proposition of this application
 - Problem domain it addresses and target users/stakeholders
 - Business context and where it fits in a larger ecosystem

 ### Technical Architecture
 - Key architectural patterns and design principles employed
 - System components and their interactions (with emphasis on interfaces)
 - Data flow diagram or processing pipeline explanation
 - Technology stack breakdown (languages, frameworks, databases, APIs)
 - Dependency analysis highlighting critical external systems

 ### Code Organization
 - Directory structure rationale and module boundaries
 - Separation of concerns implementation
 - How configuration and environment handling works
 - Testing approach and coverage strategy

 ### Notable Features
 - Unique or sophisticated implementations
 - Performance optimization techniques
 - Security considerations and implementations
 - Scalability approaches

 ### Assessment
 - Strong design choices worth preserving
 - Areas that might benefit from refactoring
 - Missing components or potential gaps
 - Technical debt indicators

 Focus on giving me a mental model of the system that would help a new developer understand both the "what" and "why" of the codebase architecture. Include any non-obvious design decisions that might reflect domain-specific requirements.
diff --git a/prompt-code-understand b/prompt-code-understand
 Explore this codebase and provide a clear overview of what this project is about. Specifically:

 1. What is the core purpose and functionality of this project?
 2. What problem does it solve or mhat service does it provide?
 3. What are the main components/modules and how do they fit together?
 4. What technologies, fremeworks, and key dependencies does it use?
 5. How is the project structured (frontend/backend/data layers)?
 6. What is the primary user flow or data flow through the application?
 7. Are there any interesting or unusual architectural decisions?
 8. What domain or industry is this project designed for?

 Just focus on helping me understand what this project is and how it works at a conceptual level rather than implementation details.
	I need you to analyze this codebase as an expert software architect. Please provide:

	### Project Overview
	- Core purpose and value proposition of this application
	- Problem domain it addresses and target users/stakeholders
	- Business context and where it fits in a larger ecosystem

	### Technical Architecture
	- Key architectural patterns and design principles employed
	- System components and their interactions (with emphasis on interfaces)
	- Data flow diagram or processing pipeline explanation
	- Technology stack breakdown (languages, frameworks, databases, APIs)
	- Dependency analysis highlighting critical external systems

	### Code Organization
	- Directory structure rationale and module boundaries
	- Separation of concerns implementation
	- How configuration and environment handling works
	- Testing approach and coverage strategy

	### Notable Features
	- Unique or sophisticated implementations
	- Performance optimization techniques
	- Security considerations and implementations
	- Scalability approaches

	### Assessment
	- Strong design choices worth preserving
	- Areas that might benefit from refactoring
	- Missing components or potential gaps
	- Technical debt indicators

	Focus on giving me a mental model of the system that would help a new developer understand both the "what" and "why" of the codebase architecture. Include any non-obvious design decisions that might reflect domain-specific requirements.
	Explore this codebase and provide a clear overview of what this project is about. Specifically:

	1. What is the core purpose and functionality of this project?
	2. What problem does it solve or mhat service does it provide?
	3. What are the main components/modules and how do they fit together?
	4. What technologies, fremeworks, and key dependencies does it use?
	5. How is the project structured (frontend/backend/data layers)?
	6. What is the primary user flow or data flow through the application?
	7. Are there any interesting or unusual architectural decisions?
	8. What domain or industry is this project designed for?

	Just focus on helping me understand what this project is and how it works at a conceptual level rather than implementation details.