分析代码库并生成一份 Markdown 入职指南,分别面向管理层、技术、业务和产品读者。
# **用于代码分析和系统文档生成的提示词** 你是一名代码分析与系统文档领域的专家。你的任务是分析本项目/工作区中提供的源代码,并生成一份全面的 Markdown 文档,作为面向多个受众(高管、技术、业务和产品)的入职指南。 ## **指令** 分析所提供的源代码,提取以下信息,并将其组织成结构清晰的 Markdown 文档: --- ## **1. 高管级视图:执行摘要** ### **应用目的** - 该系统的主要目标是什么? - 它旨在解决哪些高层级问题? ### **工作方式(高层级)** - 以简洁且易于理解的方式描述整体系统流程,供非技术人员阅读。 - 系统执行的主要步骤或流程有哪些? ### **高层级业务规则** - 识别并描述代码中实现的主要业务规则。 - 系统遵循的基本业务政策、约束或逻辑是什么? ### **关键优势** - 该系统为组织或其用户带来的主要好处是什么? --- ## **2. 技术级视图:技术概览** ### **系统架构** - 基于代码分析描述整体系统架构。 - 是否遵循特定模式(例如,单体架构 Monolithic、微服务 Microservices 等)? - 识别出的主要组件或模块有哪些? ### **使用的技术(技术栈)** - 列出项目中使用的所有编程语言、框架、库、数据库及其他技术。 ### **主要技术流程** - 详细说明系统内的主要数据流和执行流程。 - 不同组件之间如何交互? ### **关键组件** - 识别并描述最重要的系统组件,解释其在架构中的角色与职责。 ### **代码复杂度(观察结果)** - 根据你的分析,提供关于代码复杂度的一般性观察(例如,结构良好、模块化程度高、某些区域明显复杂等)。 ### **图表** - 生成高层级图表以可视化系统架构与行为: - 组件图(聚焦主要模块及其交互) - 数据流图(展示信息如何在系统中流动) - 类图(呈现关键类及其关系,如适用) - 简化部署图(显示组件运行位置,若可检测到) - 简化基础设施/部署图(若基础设施细节明显) - **使用 Mermaid 语法在 Markdown 文件中创建上述图表。图表应保持高层级,不得过于详细。** --- - **技术层面视图:** 关于系统架构、使用的技术、主要流程、关键组件以及图表(组件图、数据流图、类图和部署图)的详细信息。 - **产品视图:** 关于系统功能、目标用户、解决的问题、主要用例、功能特性以及业务领域的详细描述。 - **分析局限性:** 识别关键的分析限制,并提出克服这些限制的建议。 本次分析基于可用的源代码文件。 --- ## **重要** 分析必须考虑 **项目中的所有文件**。 阅读并理解执行任务所需的 **所有必要文件**,以实现对系统的完整理解。 --- ## **操作** 请分析我当前环境/工作区中可用的源代码,并生成所请求的 Markdown 文档。 输出文件名必须遵循以下格式: `<yyyy-mm-dd-project-name-app-discovery_cursor.md>`
# **Prompt for Code Analysis and System Documentation Generation** You are a specialist in code analysis and system documentation. Your task is to analyze the source code provided in this project/workspace and generate a comprehensive Markdown document that serves as an onboarding guide for multiple audiences (executive, technical, business, and product). ## **Instructions** Analyze the provided source code and extract the following information, organizing it into a well-structured Markdown document: --- ## **1. Executive-Level View: Executive Summary** ### **Application Purpose** - What is the main objective of this system? - What problem does it aim to solve at a high level? ### **How It Works (High-Level)** - Describe the overall system flow in a concise and accessible way for a non-technical audience. - What are the main steps or processes the system performs? ### **High-Level Business Rules** - Identify and describe the main business rules implemented in the code. - What are the fundamental business policies, constraints, or logic that the system follows? ### **Key Benefits** - What are the main benefits this system delivers to the organization or its users? --- ## **2. Technical-Level View: Technology Overview** ### **System Architecture** - Describe the overall system architecture based on code analysis. - Does it follow a specific pattern (e.g., Monolithic, Microservices, etc.)? - What are the main components or modules identified? ### **Technologies Used (Technology Stack)** - List all programming languages, frameworks, libraries, databases, and other technologies used in the project. ### **Main Technical Flows** - Detail the main data and execution flows within the system. - How do the different components interact with each other? ### **Key Components** - Identify and describe the most important system components, explaining their role and responsibility within the architecture. ### **Code Complexity (Observations)** - Based on your analysis, provide general observations about code complexity (e.g., well-structured, modularized, areas of higher apparent complexity). ### **Diagrams** - Generate high-level diagrams to visualize the system architecture and behavior: - Component diagram (focusing on major modules and their interactions) - Data flow diagram (showing how information moves through the system) - Class diagram (presenting key classes and their relationships, if applicable) - Simplified deployment diagram (showing where components run, if detectable) - Simplified infrastructure/deployment diagram (if infrastructure details are apparent) - **Create the diagrams above using Mermaid syntax within the Markdown file. Diagrams should remain high-level and not overly detailed.** --- ## **3. Product View: Product Summary** ### **What the System Does (Detailed)** - Describe the system’s main functionalities in detail. - What tasks or actions can users perform? ### **Who the System Is For (Users / Customers)** - Identify the primary target audience of the system. - Who are the end users or customers who benefit from it? ### **Problems It Solves (Needs Addressed)** - What specific problems does the system help solve for users or the organization? - What needs does it address? ### **Use Cases / User Journeys (High-Level)** - What are the main use cases of the system? - How do users interact with the system to achieve their goals? ### **Core Features** - List the most important system features clearly and concisely. ### **Business Domains** - Identify the main business domains covered by the system (e.g., sales, inventory, finance). --- ## **Analysis Limitations** - What were the main limitations encountered during the code analysis? - Briefly describe what constrained your understanding of the code. - Provide suggestions to reduce or eliminate these limitations. --- ## **Document Guidelines** ### **Document Format** - The document must be formatted in Markdown, with clear titles and subtitles for each section. - Use lists, tables, and other Markdown elements to improve readability and comprehension. ### **Additional Instructions** - Focus on delivering relevant, high-level information, avoiding excessive implementation details unless critical for understanding. - Use clear, concise, and accessible language suitable for multiple audiences. - Be as specific as possible based on the code analysis. - Generate the complete response as a **well-formatted Markdown (`.md`) document**. - Use **clear and direct language**. - Use **headings and subheadings** according to the sections above. ### **Document Title** **Executive and Business Analysis of the Application – "<application-name>"** ### **Document Summary** This document is the result of the source code analysis of the <system-name> system and covers the following areas: - **Executive-Level View:** Summary of the application’s purpose, high-level operation, main business rules, and key benefits. - **Technical-Level View:** Details about system architecture, technologies used, main flows, key components, and diagrams (components, data flow, classes, and deployment). - **Product View:** Detailed description of system functionality, target users, problems addressed, main use cases, features, and business domains. - **Analysis Limitations:** Identification of key analysis constraints and suggestions to overcome them. The analysis was based on the available source code files. --- ## **IMPORTANT** The analysis must consider **ALL project files**. Read and understand **all necessary files** required to perform the task and achieve a complete understanding of the system. --- ## **Action** Please analyze the source code currently available in my environment/workspace and generate the requested Markdown document. The output file name must follow this format: `<yyyy-mm-dd-project-name-app-discovery_cursor.md>`