Please carefully review the highlighted code for any issues. Focus on:
  - Syntax errors
  - Logic errors
  - Security vulnerabilities
  - Performance bottlenecks
Provide detailed explanations for each issue found and suggest improvements.

Based on the provided feature documentation, generate a comprehensive development plan. Include:
  - Feature name and description
  - User types and their needs
  - Acceptance criteria
  - Development strategy and steps (e.g., Domain Models, Database Layer, API Integration)
  - Validation checklist to ensure completeness
Ensure the plan aligns with existing architecture and avoids duplication.

Translate the provided feature documentation into a combined document that fits the existing codebase. Ensure:
  - Consistency with current patterns and naming conventions
  - No duplication of files or database tables
  - Clear mapping of features to their technical implementation (e.g., models, APIs, UI components)
Save the output as `Feature-name-Combined.md`.

Review the provided database schema design. Check for:
  - Normalization issues (e.g., redundancy or dependency problems)
  - Missing relationships or constraints
  - Scalability concerns (e.g., indexing or partitioning)
  - Security risks (e.g., sensitive data storage)
Suggest improvements to optimize performance and maintainability.

Write detailed testing instructions for the new feature. Include:
  - Login steps for different user roles (e.g., admin, regular user)
  - Navigation paths to access the feature
  - Expected results or success messages at each step
  - Error conditions to test (e.g., invalid inputs, edge cases)
Ensure that all acceptance criteria are covered in the tests.

Perform a thorough check of the application to identify any issues. Focus on:
  - Broken URLs or navigation paths
  - TypeScript errors in the codebase
  - API errors or unexpected responses
Provide a report of all identified issues along with suggested fixes.

Analyze the current codebase structure and suggest improvements. Consider:
  - Folder organization and file naming conventions
  - Separation of concerns (e.g., modularization of components, services, utilities)
  - Removal of unused files or redundant code
Provide actionable recommendations to enhance readability and maintainability.

Review the provided external API integration guide. Ensure that it includes:
  - Clear setup instructions (e.g., authentication, configuration)
  - Examples of API usage (e.g., sample requests and responses)
  - Error handling guidelines (e.g., handling rate limits, retries)
Suggest any missing details or improvements to make it more comprehensive.