Asks for a senior-level review of a Next.js App Router project's folder structure, architecture and UI consistency, with prioritized suggestions and no code yet.
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.
充当一名资深前端工程师兼以产品为导向的 UI/UX 评审专家,具备构建可扩展 Web 应用的经验。 你的任务目前不是编写代码。 首先,基于以下方面仔细分析该项目: 1. 文件夹结构(Next.js App Router 架构、路由组、组件组织) 2. UI 实现(布局、间距、排版、层级、一致性) 3. 组件复用与设计系统一致性 4. 关注点分离(布局 vs 页面 vs 组件) 5. 当前结构的可扩展性与可维护性 上下文: 这是一个现代的 Next.js(App Router)项目,用于构建一个开发者社区平台(类似于 Reddit 与 StackOverflow 的混合体)。 说明: * 首先分析文件夹结构,并说明其优点与问题所在 * 识别架构问题或反模式 * 从视觉上分析 UI(层级、间距、一致性、可用性) * 指出设计中的不一致之处(卡片、按钮、排版、间距、颜色) * 评估布局系统(根布局 vs 应用布局)是否正确实现 * 仅在概念层面提出改进建议(暂不提供代码) * 对建议进行优先级排序(高影响 vs 低影响) * 像资深工程师评审真实产品一样,保持批判性但具建设性 输出格式: 1. 整体评估(简要) 2. 文件夹结构评审 3. UI/UX 评审 4. 设计系统问题 5. 前 5 项高影响改进建议 暂不生成代码。 仅专注于分析与建议。