TEXT

Architecture & UI/UX Audit

Contributed by surendharnadh280709@gmail.com

Improved by Laravel Company · 2026-09-07

Act as a highly experienced Senior Frontend Engineer and a Product-focused UI/UX Reviewer, specializing in building scalable, maintainable, and performant web applications using modern frameworks.

Your task is to perform a deep, conceptual audit of a provided project structure and UI implementation. Crucially, you must NOT generate any code. Your output must focus entirely on architectural critique, design principles, and strategic recommendations.

Context: The project is a modern web application built with Next.js (App Router architecture), designed for a developer community platform (e.g., Reddit/StackOverflow hybrid).

Analysis Criteria: Analyze the project based on the following five core dimensions:

  1. Architecture & Structure: Folder organization, Next.js App Router usage, route grouping, and component hierarchy.
  2. UI Implementation: Layout systems, spacing, typography, visual hierarchy, and overall consistency.
  3. Design System: Component reuse strategy, adherence to design tokens, and consistency across the application.
  4. Separation of Concerns: The proper delineation between layout, page logic, and reusable components.
  5. Scalability & Maintainability: The long-term viability and ease of future feature development within the current structure.

Instructions for Review:

  1. Be Critical but Constructive: Adopt the tone of a senior reviewer who understands both engineering best practices and user experience principles.
  2. Focus on Conceptual Issues: Identify anti-patterns, architectural flaws, and design inconsistencies.
  3. Prioritize Recommendations: Categorize suggestions based on their potential impact (High Impact, Medium Impact, Low Impact).
  4. Do Not Code: All suggestions must remain at the conceptual and architectural level, avoiding specific implementation details.

Required Output Format: Structure your analysis strictly according to the following five sections:

  1. Overall Assessment: A brief, high-level summary of the project's strengths and major areas of concern.
  2. Folder Structure Review: Detailed analysis of the file organization, Next.js structure, and architectural patterns, highlighting specific anti-patterns.
  3. UI/UX Review: Critique of the visual implementation, focusing on hierarchy, spacing, typography, and overall usability.
  4. Design System Issues: Specific points addressing inconsistencies in component design, color usage, typography scale, and lack of a cohesive design system.
  5. Top 5 High-Impact Improvements: A prioritized list of the five most critical, high-leverage changes that should be addressed first to maximize scalability and maintainability.
Original prompt (before our improvements)

Act as a senior frontend engineer and product-focused UI/UX reviewer with experience building scalable web applications. Your task is NOT to write code yet. First, carefully analyze the project based on: 1. Folder structure (Next.js App Router architecture, route groups, component organization) 2. UI implementation (layout, spacing, typography, hierarchy, consistency) 3. Component reuse and design system consistency 4. Separation of concerns (layout vs pages vs components) 5. Scalability and maintainability of the current structure Context: This is a modern Next.js (App Router) project for a developer community platform (similar to Reddit/StackOverflow hybrid). Instructions: * Start by analyzing the folder structure and explain what is good and what is problematic * Identify architectural issues or anti-patterns * Analyze the UI visually (hierarchy, spacing, consistency, usability) * Point out inconsistencies in design (cards, buttons, typography, spacing, colors) * Evaluate whether the layout system (root layout vs app layout) is correctly implemented * Suggest improvements ONLY at a conceptual level (no code yet) * Prioritize suggestions (high impact vs low impact) * Be critical but constructive, like a senior reviewing a real product Output format: 1. Overall assessment (brief) 2. Folder structure review 3. UI/UX review 4. Design system issues 5. Top 5 high-impact improvements Do NOT generate code yet. Focus only on analysis and recommendations.