Skip to content
LiveNew tools this week
Submit
AIMarketly

Architecture & UI/UX Audit

It asks an AI to assume the persona of a Senior Frontend Engineer & Product Reviewer to perform a high-level critique of a Next.js (App Router) project. Instead of writing code, the prompt focuses on evaluating the architecture (folder stru

Web development3saves0 views

About

It asks an AI to assume the persona of a Senior Frontend Engineer & Product Reviewer to perform a high-level critique of a Next.js (App Router) project. Instead of writing code, the prompt focuses on evaluating the architecture (folder structure, scalability), UI/UX (hierarchy, consistency), and design system (component reuse) of a developer community platform to identify anti-patterns and suggest high-impact improvements.

Prompt

Full instructions — copy and paste into your model

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.