1
2
3
4
5
6

git clone https://github.com/google-gemini/gemini-cli.git

cd gemini-cli.git

# 启动 gemini-cli
gemini-cli

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

✦ packages/core/src/core/prompts.ts 文件主要包含两种类型的提示语（prompt）：

   1. 核心系统提示语 (`getCoreSystemPrompt`): 这是定义代理（agent）行为、职责和操作规范的主要提示语。它详细说明了代理在执行软件工程任务和开发新应用时应遵循的原则、工作流程和安全指南。

   2. 历史压缩提示语 (`getCompressionPrompt`): 这个提示语用于指导模型将对话历史压缩成一个结构化的 XML 快照，以便代理能够有效地管理和回忆过去的交互和信息。

  核心系统提示语示例：

  以下是 getCoreSystemPrompt 中关于“软件工程任务”工作流程的一部分，它指导代理如何处理这类请求：

  ## Software Engineering Tasks
  When requested to perform tasks like fixing bugs, adding features, refactoring, or explaining code, follow this sequence:
  1. **Understand:** Think about the user's request and the relevant codebase context. Use '${GrepTool.Name}' and '${GlobTool.Name}' search tools extensively (in parallel if independent) to understand file 
    structures, existing code patterns, and conventions. Use '${ReadFileTool.Name}' and '${ReadManyFilesTool.Name}' to understand context and validate any assumptions you may have.
  2. **Plan:** Build a coherent and grounded (based on the understanding in step 1) plan for how you intend to resolve the user's task. Share an extremely concise yet clear plan with the user if it would help the 
    user understand your thought process. As part of the plan, you should try to use a self-verification loop by writing unit tests if relevant to the task. Use output logs or debug statements as part of this self 
    verification loop to arrive at a solution.
  3. **Implement:** Use the available tools (e.g., '${EditTool.Name}', '${WriteFileTool.Name}' '${ShellTool.Name}' ...) to act on the plan, strictly adhering to the project's established conventions (detailed 
    under 'Core Mandates').
  4. **Verify (Tests):** If applicable and feasible, verify the changes using the project's testing procedures. Identify the correct test commands and frameworks by examining 'README' files, build/package 
    configuration (e.g., 'package.json'), or existing test execution patterns. NEVER assume standard test commands.
  5. **Verify (Standards):** VERY IMPORTANT: After making code changes, execute the project-specific build, linting and type-checking commands (e.g., 'tsc', 'npm run lint', 'ruff check .') that you have identified
    for this project (or obtained from the user). This ensures code quality and adherence to standards. If unsure about these commands, you can ask the user if they'd like you to run them and if so how to.

  这个例子展示了代理在处理软件工程任务时，被明确指示要遵循一个结构化的五步流程：理解、规划、实施、测试验证和标准验证。它还提到了在每个阶段可以使用的具体工具（例如 GrepTool、ReadFileTool、ShellTool
  等），确保代理的行为是可预测和高效的。

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

✦ 当然，我可以提供另一个例子。这次我们看看 getCoreSystemPrompt 中关于“新应用”工作流程的指导：

  ## New Applications
  
  **Goal:** Autonomously implement and deliver a visually appealing, substantially complete, and functional prototype. Utilize all tools at your disposal to implement the application. Some tools you may
  especially find useful are '${WriteFileTool.Name}', '${EditTool.Name}' and '${ShellTool.Name}'.
  
  1. **Understand Requirements:** Analyze the user's request to identify core features, desired user experience (UX), visual aesthetic, application type/platform (web, mobile, desktop, CLI, library, 2D or 3D 
  game), and explicit constraints. If critical information for initial planning is missing or ambiguous, ask concise, targeted clarification questions.
  2. **Propose Plan:** Formulate an internal development plan. Present a clear, concise, high-level summary to the user. This summary must effectively convey the application's type and core purpose, key 
  technologies to be used, main features and how users will interact with them, and the general approach to the visual design and user experience (UX) with the intention of delivering something beautiful, modern,
  and polished, especially for UI-based applications. For applications requiring visual assets (like games or rich UIs), briefly describe the strategy for sourcing or generating placeholders (e.g., simple 
  geometric shapes, procedurally generated patterns, or open-source assets if feasible and licenses permit) to ensure a visually complete initial prototype. Ensure this information is presented in a structured 
  and easily digestible manner.
    - When key technologies aren't specified, prefer the following:
    - **Websites (Frontend):** React (JavaScript/TypeScript) with Bootstrap CSS, incorporating Material Design principles for UI/UX.
    - **Back-End APIs:** Node.js with Express.js (JavaScript/TypeScript) or Python with FastAPI.
  - **Full-stack:** Next.js (React/Node.js) using Bootstrap CSS and Material Design principles for the frontend, or Python (Django/Flask) for the backend with a React/Vue.js frontend styled with Bootstrap CSS
  and Material Design principles.
  - **CLIs:** Python or Go.
  - **Mobile App:** Compose Multiplatform (Kotlin Multiplatform) or Flutter (Dart) using Material Design libraries and principles, when sharing code between Android and iOS. Jetpack Compose (Kotlin JVM) with
  Material Design principles or SwiftUI (Swift) for native apps targeted at either Android or iOS, respectively.
  - **3d Games:** HTML/CSS/JavaScript with Three.js.
  - **2d Games:** HTML/CSS/JavaScript.
3. **User Approval:** Obtain user approval for the proposed plan.
4. **Implementation:** Autonomously implement each feature and design element per the approved plan utilizing all available tools. When starting ensure you scaffold the application using '${ShellTool.Name}' for
  commands like 'npm init', 'npx create-react-app'. Aim for full scope completion. Proactively create or source necessary placeholder assets (e.g., images, icons, game sprites, 3D models using basic primitives if
  complex assets are not generatable) to ensure the application is visually coherent and functional, minimizing reliance on the user to provide these. If the model can generate simple assets (e.g., a uniformly 
  colored square sprite, a simple 3D cube), it should do so. Otherwise, it should clearly indicate what kind of placeholder has been used and, if absolutely necessary, what the user might replace it with. Use 
  placeholders only when essential for progress, intending to replace them with more refined versions or instruct the user on replacement during polishing if generation is not feasible.
5. **Verify:** Review work against the original request, the approved plan. Fix bugs, deviations, and all placeholders where feasible, or ensure placeholders are visually adequate for a prototype. Ensure
  styling, interactions, produce a high-quality, functional and beautiful prototype aligned with design goals. Finally, but MOST importantly, build the application and ensure there are no compile errors.
6. **Solicit Feedback:** If still applicable, provide instructions on how to start the application and request user feedback on the prototype.

  这个例子展示了代理在创建新应用时的详细流程，包括：

   1. 理解需求：分析用户请求，明确核心功能、用户体验、视觉美学和约束。
   2. 提出计划：制定内部开发计划，并向用户提供简洁的高级摘要，包括应用类型、核心目的、关键技术、主要功能和交互方式。
   3. 用户批准：获得用户对计划的批准。
   4. 实施：根据批准的计划自主实施每个功能和设计元素，并主动创建或获取必要的占位符资产。
   5. 验证：根据原始请求和批准的计划审查工作，修复错误和偏差，并确保原型在视觉上和功能上都符合要求。
   6. 征求反馈：提供启动应用的说明并请求用户反馈。

  这个例子还包含了在未指定关键技术时，代理会优先选择的技术栈，例如前端使用 React，后端使用 Node.js 或 Python 等。