1
This commit is contained in:
zhoutianchi
@@ -1,126 +0,0 @@
|
||||
---
|
||||
description:
|
||||
globs:
|
||||
alwaysApply: false
|
||||
---
|
||||
# AI Agent Protocol: Self-Contained Mandatory Interactive Final Review Loop with Auto-Script Creation (Version 3)
|
||||
|
||||
## 0. User Advisory & Safety:
|
||||
This is an advanced, experimental rule. It instructs the AI Agent to check for, potentially create, and then execute a Python script (`final_review_gate.py`) in your project's root directory to facilitate an interactive review loop. By using this rule, you acknowledge that the AI will attempt file system operations (read, write, execute) as directed. Ensure the AI's execution environment has appropriate permissions if you expect script auto-creation to work, and be aware of the security implications.
|
||||
|
||||
## 1. Core Principle & Context:
|
||||
Your primary task processing includes a **mandatory final interactive review stage** driven by user input through a specific Python script (`final_review_gate.py`). You are NOT to consider your overall task complete until this review stage explicitly signals completion. This protocol leverages your known capability to run commands in a sub-terminal (displayed within the chat interface) and read their output.
|
||||
|
||||
## Phase 0: Ensure `final_review_gate.py` Script Exists
|
||||
(This phase is executed ONCE per user request that triggers this overall protocol, or if the script is missing or its content is incorrect.)
|
||||
|
||||
1. **Define Script Details:**
|
||||
* **Script Name:** `final_review_gate.py`
|
||||
* **Target Location:** Directly in the root of the current project/workspace.
|
||||
* **Python Script Content (ensure this exact content is used):**
|
||||
```python
|
||||
# final_review_gate.py
|
||||
import sys
|
||||
import os
|
||||
|
||||
if __name__ == "__main__":
|
||||
# Try to make stdout unbuffered for more responsive interaction.
|
||||
# This might not work on all platforms or if stdout is not a TTY,
|
||||
# but it's a good practice for this kind of interactive script.
|
||||
try:
|
||||
sys.stdout = os.fdopen(sys.stdout.fileno(), 'w', buffering=1)
|
||||
except Exception:
|
||||
pass # Ignore if unbuffering fails, e.g., in certain environments
|
||||
|
||||
try:
|
||||
sys.stderr = os.fdopen(sys.stderr.fileno(), 'w', buffering=1)
|
||||
except Exception:
|
||||
pass # Ignore
|
||||
|
||||
print("--- FINAL REVIEW GATE ACTIVE ---", flush=True)
|
||||
print("AI has completed its primary actions. Awaiting your review or further sub-prompts.", flush=True)
|
||||
print("Type your sub-prompt, or one of: 'TASK_COMPLETE', 'Done', 'Quit', 'q' to signal completion.", flush=True) # MODIFIED
|
||||
|
||||
active_session = True
|
||||
while active_session:
|
||||
try:
|
||||
# Signal that the script is ready for input.
|
||||
# The AI doesn't need to parse this, but it's good for user visibility.
|
||||
print("REVIEW_GATE_AWAITING_INPUT:", end="", flush=True)
|
||||
|
||||
line = sys.stdin.readline()
|
||||
|
||||
if not line: # EOF
|
||||
print("--- REVIEW GATE: STDIN CLOSED (EOF), EXITING SCRIPT ---", flush=True)
|
||||
active_session = False
|
||||
break
|
||||
|
||||
user_input = line.strip()
|
||||
|
||||
# Check for exit conditions
|
||||
if user_input.upper() in ['TASK_COMPLETE', 'DONE', 'QUIT', 'Q']: # MODIFIED: Empty string no longer exits
|
||||
print(f"--- REVIEW GATE: USER SIGNALED COMPLETION WITH '{user_input.upper()}' ---", flush=True)
|
||||
active_session = False
|
||||
break
|
||||
elif user_input: # If there's any other non-empty input (and not a completion command)
|
||||
# This is the critical line the AI will "listen" for.
|
||||
print(f"USER_REVIEW_SUB_PROMPT: {user_input}", flush=True)
|
||||
# If user_input was empty (and not a completion command),
|
||||
# the loop simply continues, and "REVIEW_GATE_AWAITING_INPUT:" will be printed again.
|
||||
|
||||
except KeyboardInterrupt:
|
||||
print("--- REVIEW GATE: SESSION INTERRUPTED BY USER (KeyboardInterrupt) ---", flush=True)
|
||||
active_session = False
|
||||
break
|
||||
except Exception as e:
|
||||
print(f"--- REVIEW GATE SCRIPT ERROR: {e} ---", flush=True)
|
||||
active_session = False
|
||||
break
|
||||
|
||||
print("--- FINAL REVIEW GATE SCRIPT EXITED ---", flush=True)
|
||||
```
|
||||
|
||||
2. **Ensure Script Existence and Correctness:**
|
||||
a. Use your file system tools to check if the file `final_review_gate.py` exists in the project root.
|
||||
b. **If the file `final_review_gate.py` does NOT exist OR if its content does not EXACTLY match the Python script provided in section "Phase 0.1.Python Script Content" (you may need to read the existing file and compare):**
|
||||
i. You MUST create or overwrite the `final_review_gate.py` file in the project root.
|
||||
ii. The content of this file MUST be *exactly* the Python script content provided above. Ensure all indentation, comments, and lines are preserved perfectly. Use your "create file" or "edit file" tool.
|
||||
iii. After creating/overwriting it, announce: "The `final_review_gate.py` script has been created/updated in the project root with the latest interaction enhancements."
|
||||
c. **If the file `final_review_gate.py` already exists and its content is correct:** You may skip announcing its creation.
|
||||
d. If you encounter any errors checking for, reading, or creating/writing the file (e.g., permission issues), you MUST report this to the user. State clearly: "Error managing `final_review_gate.py`: [specific error]. Cannot proceed with interactive review." and then conclude the interaction for the main task as best as you can without this interactive step.
|
||||
|
||||
## Phase 1: Primary Task Execution
|
||||
1. Address the user's main request as you normally would: perform analysis, make code changes, call tools, and run applications/tests in sub-terminals if the main task requires it.
|
||||
* **Application Execution Confirmation:** Before attempting to run an entire application (e.g., a web server, a full front-end build, a long-running background process), you MUST ask the user for explicit confirmation. For example: "I am about to run the [application name/command]. Is it okay to proceed, or is it possibly already running?"
|
||||
* This confirmation is NOT required for running individual test scripts, linters, build tools for specific components, or other non-application-level commands necessary for task completion.
|
||||
* If the user indicates an application is already running or denies permission, adapt your strategy accordingly (e.g., focus on tests or specific file executions).
|
||||
2. Leverage your ability to read outputs/errors from these sub-terminals to make iterative fixes during *this* primary phase.
|
||||
|
||||
## Phase 2: Mandatory Final Interactive Review Script Execution
|
||||
1. **Transition Point:** Once you believe you have completed all substantive actions for the user's initial request (Phase 1), **DO NOT CONCLUDE THE CONVERSATION**. You MUST now transition to this Final Interactive Review phase.
|
||||
2. **Action:** Execute the `final_review_gate.py` script (which you ensured exists and is correct in Phase 0) from the project root.
|
||||
* Determine the correct Python interpreter command (e.g., `python`, `python3`) available in the execution environment. A robust command attempt would be `python3 ./final_review_gate.py` and if that fails, try `python ./final_review_gate.py`.
|
||||
* **Crucially, the terminal for this script MUST run directly within the chat window, and its output MUST be continuously visible to the user as it is generated.** It must NOT pop open as a separate window or run hidden in the background. You MUST wait for the script (and its terminal interaction) to fully complete and exit before you proceed with any further actions or attempt to conclude the overall task. Your processing will be blocked by this script's execution.
|
||||
3. **Announcement:** Clearly inform the user: "I have completed the primary actions. Now initiating the mandatory Final Interactive Review by running `./final_review_gate.py`. The review terminal is now active **in this chat window, and its output will be displayed live**. Please provide any sub-prompts directly into that script's input area, or type 'TASK_COMPLETE', 'Done', 'Quit', or 'q' when satisfied." (MODIFIED: Removed "or simply press Enter")
|
||||
|
||||
## Phase 3: Interactive Review Loop (Monitoring Script Output)
|
||||
1. **Active Monitoring & Display:** Continuously monitor the standard output (stdout) of the launched `final_review_gate.py` script **as it appears live in the chat window**. Ensure the user sees all script output, including the `REVIEW_GATE_AWAITING_INPUT:` prompt. You will "read" its output using the same capability that allows you to read terminal logs or error messages. The script will loop and re-prompt if an empty input is given.
|
||||
2. **User Sub-Prompt Detection:** When the script's stdout prints a line formatted EXACTLY as:
|
||||
`USER_REVIEW_SUB_PROMPT: <user's sub-prompt text>`
|
||||
You MUST interpret `<user's sub-prompt text>` as a new, direct, actionable instruction from the user.
|
||||
3. **Processing Sub-Prompts:**
|
||||
a. This instruction is a continuation or refinement of the *original, still-active task*.
|
||||
b. Analyze the sub-prompt. Execute any necessary actions (code changes, new tool calls, file operations, etc.). **All tool calls made during this phase are part of the original request's tool call budget.** If the sub-prompt requests running an entire application, the confirmation principle from "Phase 1, Step 1 (Application Execution Confirmation)" applies.
|
||||
c. Provide feedback or results of these actions in the main chat interface as you normally would for any AI action.
|
||||
d. After processing the sub-prompt and giving feedback in the chat, IMMEDIATELY return your focus to monitoring the `final_review_gate.py` script's terminal output (which remains live and visible in the chat) for the next user instruction or completion signal. This loop is critical.
|
||||
4. **Completion Signal Detection:** The interactive review loop continues until the script's stdout (visible in the chat window) prints a line containing:
|
||||
* `--- REVIEW GATE: USER SIGNALED COMPLETION WITH 'TASK_COMPLETE' ---` (or 'DONE', 'QUIT', 'Q' as per script logic)
|
||||
* OR `--- FINAL REVIEW GATE SCRIPT EXITED ---` (or any other script exit/error message like `REVIEW GATE: STDIN CLOSED` or `REVIEW GATE SCRIPT ERROR:`)
|
||||
(MODIFIED: Removed specific "EMPTY INPUT RECEIVED" as a completion signal, as the script no longer behaves this way for completion.)
|
||||
|
||||
## Phase 4: True Task Conclusion
|
||||
1. Only after the `final_review_gate.py` script has terminated (as observed by its terminal session in the chat window closing and its final exit messages being printed and visible) are you permitted to consider the user's original request fully satisfied.
|
||||
2. You may then provide your final summary of all actions taken throughout all phases (including the interactive review).
|
||||
|
||||
## Overriding Default Behavior:
|
||||
This entire "Final Interactive Review" process (Phases 0, 2, 3, and 4) is a **strict, non-negotiable requirement** that overrides any default tendency you have to end the conversation after completing Phase 1. The task is only finished when the user explicitly confirms with one of the specified keywords through the review script or the script otherwise terminates due to an error or EOF (as per the defined behavior, including the in-chat, blocking, and continuously visible terminal execution). Your "sense of completion" for the original request is deferred until this interactive review is done.
|
||||
@@ -1,8 +0,0 @@
|
||||
---
|
||||
description: Best practices for Axios HTTP requests
|
||||
globs: *.ts,*.vue
|
||||
alwaysApply: false
|
||||
---
|
||||
- Refer to `src/api/admin/audit.ts` as a template to make an API call with the same effect
|
||||
- The API method must be called using the synchronous syntax await, and then the result is deconstructed
|
||||
- All axios call logic needs to be placed in `src/api`
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
description: Best practices for Daisy UI
|
||||
globs: *.vue
|
||||
alwaysApply: false
|
||||
---
|
||||
- Use Daisy UI classes for consistent theming
|
||||
- All colors and themes should be consistent with the overall UI element-plus. Please refer to `src/theme/element.scss`
|
||||
- Implement Daisy UI buttons and form controls for UI consistency
|
||||
- Customize themes using Daisy UI's theme system
|
||||
- Ensure responsive design with Daisy UI's responsive classes
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
description: Best practices for using Element Plus components
|
||||
globs: *.vue
|
||||
alwaysApply: false
|
||||
---
|
||||
- Use Element Plus components for rich UI functionality
|
||||
- Implement proper form validation with Element Plus forms
|
||||
- Customize Element Plus themes using SCSS variables
|
||||
- Utilize Element Plus's built-in internationalization support
|
||||
@@ -1,11 +0,0 @@
|
||||
---
|
||||
description:
|
||||
globs:
|
||||
alwaysApply: true
|
||||
---
|
||||
# MCP Interactive Feedback 规则
|
||||
|
||||
1. 在任何流程、任务、对话进行时，无论是询问、回复、或完成阶段性任务，皆必须调用 MCP mcp-feedback-enhanced。
|
||||
2. 每当收到用户反馈，若反馈内容非空，必须再次调用 MCP mcp-feedback-enhanced，并根据反馈内容调整行为。
|
||||
3. 仅当用户明确表示「结束」或「不再需要交互」时，才可停止调用 MCP mcp-feedback-enhanced，流程才算结束。
|
||||
4. 除非收到结束指令，否则所有步骤都必须重复调用 MCP mcp-feedback-enhanced。
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
description: Best practices for state management with Pinia
|
||||
globs: src/stores/*.ts
|
||||
alwaysApply: false
|
||||
---
|
||||
- Use Pinia stores for global state management
|
||||
- Implement getters for computed state
|
||||
- Use actions for side effects and asynchronous operations
|
||||
- Utilize `defineStore` with `id` for better store organization
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
description: Best practices for Tailwind CSS
|
||||
globs: *.vue
|
||||
alwaysApply: false
|
||||
---
|
||||
- Implement responsive design with Tailwind's responsive modifiers
|
||||
- All colors and themes should be consistent with the overall UI element-plus. Please refer to `src/theme/element.scss`
|
||||
- Customize Tailwind's default theme using `tailwind.config.js`
|
||||
- Use `@apply` directive for component-level styling
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
description: TypeScript coding standards and type safety guidelines
|
||||
globs: *.vue,*.ts
|
||||
alwaysApply: false
|
||||
---
|
||||
- Use strict null checks for better type safety
|
||||
- Prefer interfaces over types for object shapes
|
||||
- Use type guards and assertions for runtime type checking
|
||||
- Implement proper type inference for cleaner code
|
||||
- Use enums for a set of named constants
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
description: Best practices for Vue 3 applications
|
||||
globs: *.vue
|
||||
alwaysApply: false
|
||||
---
|
||||
- Use Vue3 Composition API for better code organization and reusability
|
||||
- Components should be automatically split into multiple small components that are easy to maintain
|
||||
- parseTime/parseDate/baseURL are global properties and can be used directly
|
||||
- Leverage Vue's built-in directives like `v-model` for form handling
|
||||
- Implement proper error handling with `try/catch` in component setup
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
description: Best practices for Vue I18n internationalization
|
||||
globs: *.vue,*.ts
|
||||
alwaysApply: false
|
||||
---
|
||||
- Use Vue I18n for managing translations
|
||||
- Use `const { t } = useI18n()` in Vue components to use t('area.areaType') as a placeholder
|
||||
- The global I18N translation files are in `src/i18n`
|
||||
- The Chinese and English I18N file names use 'zh-cn.ts' and' en.ts' and save them in the 'i18n' folder in the current directory
|
||||
- The key values in the language file are named by the hump
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
description: Best practices for Vue Router 4 configuration and usage
|
||||
globs: src/router/*.ts
|
||||
alwaysApply: false
|
||||
---
|
||||
- Use named routes for better maintainability
|
||||
- Implement route-level code-splitting for performance
|
||||
- Use navigation guards for route protection and redirection
|
||||
- Leverage route meta fields for additional route information
|
||||
@@ -1,8 +0,0 @@
|
||||
---
|
||||
description: Best practices for using VueUse composables
|
||||
globs: *.ts,*.vue
|
||||
alwaysApply: false
|
||||
---
|
||||
- Use VueUse composables to enhance reactivity and performance
|
||||
- Consider reusing existing utility classes including vueuse to avoid duplication of code
|
||||
- The current tool package is in `src/utils/*.ts`
|
||||
4
.env
4
.env
@@ -1,8 +1,8 @@
|
||||
# 网站主标题
|
||||
VITE_GLOBAL_TITLE= 'PIGX AI'
|
||||
VITE_GLOBAL_TITLE= '江苏省常州技师学院'
|
||||
|
||||
# footer
|
||||
VITE_FOOTER_TITLE= '©2025 pig4cloud.com'
|
||||
VITE_FOOTER_TITLE= '©2025 cyweb'
|
||||
|
||||
# 是否是微服务架构（重要）
|
||||
VITE_IS_MICRO= true
|
||||
|
||||
3
.gitignore
vendored
3
.gitignore
vendored
@@ -30,4 +30,5 @@ yarn.lock
|
||||
pnpm-lock.yaml
|
||||
|
||||
# cursor review
|
||||
final_review_gate.py
|
||||
final_review_gate.py
|
||||
.cursor/
|
||||
@@ -66,7 +66,7 @@
|
||||
"vue-echarts": "7.0.3",
|
||||
"vue-i18n": "9.2.2",
|
||||
"vue-json-viewer": "^3.0.4",
|
||||
"vue-router": "^4.1.6",
|
||||
"vue-router": "4.1.6",
|
||||
"vue3-tree-org": "^4.2.2",
|
||||
"vue3-video-play": "1.3.1-beta.6",
|
||||
"vuedraggable": "^4.1.0"
|
||||
|
||||
@@ -64,14 +64,14 @@
|
||||
>
|
||||
{{ $t('mobile.backToLogin') }}
|
||||
</a>
|
||||
<a
|
||||
href="#"
|
||||
v-if="autoRegisterEnable"
|
||||
class="ml-2 text-blue-500 hover:text-blue-400 dark:text-blue-400 dark:hover:text-blue-300"
|
||||
@click="emit('change', LoginTypeEnum.REGISTER)"
|
||||
>
|
||||
{{ $t('mobile.createAccount') }}
|
||||
</a>
|
||||
<!-- <a-->
|
||||
<!-- href="#"-->
|
||||
<!-- v-if="autoRegisterEnable"-->
|
||||
<!-- class="ml-2 text-blue-500 hover:text-blue-400 dark:text-blue-400 dark:hover:text-blue-300"-->
|
||||
<!-- @click="emit('change', LoginTypeEnum.REGISTER)"-->
|
||||
<!-- >-->
|
||||
<!-- {{ $t('mobile.createAccount') }}-->
|
||||
<!-- </a>-->
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
@@ -22,7 +22,9 @@
|
||||
:placeholder="$t('password.accountPlaceholder2')"
|
||||
v-model="state.ruleForm.password"
|
||||
class="dark:bg-slate-700 dark:text-slate-200"
|
||||
autocomplete="off"
|
||||
autocomplete="new-password"
|
||||
:readonly="state.passwordReadonly"
|
||||
@focus="state.passwordReadonly = false"
|
||||
>
|
||||
<template #prefix>
|
||||
<el-icon class="el-input__icon dark:text-slate-400">
|
||||
@@ -65,9 +67,9 @@
|
||||
<a href="#" class="text-blue-500" @click="emit('change', LoginTypeEnum.MOBILE)">
|
||||
{{ $t('password.mobileLogin') }}
|
||||
</a>
|
||||
<a href="#" v-if="autoRegisterEnable" class="ml-2 text-blue-500" @click="emit('change', LoginTypeEnum.REGISTER)">
|
||||
{{ $t('password.createAccount') }}
|
||||
</a>
|
||||
<!-- <a href="#" v-if="autoRegisterEnable" class="ml-2 text-blue-500" @click="emit('change', LoginTypeEnum.REGISTER)">-->
|
||||
<!-- {{ $t('password.createAccount') }}-->
|
||||
<!-- </a>-->
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -84,7 +86,7 @@
|
||||
</template>
|
||||
|
||||
<script setup lang="ts" name="password">
|
||||
import { defineAsyncComponent, reactive, ref } from 'vue';
|
||||
import { defineAsyncComponent, onMounted, reactive, ref } from 'vue';
|
||||
import { useUserInfo } from '/@/stores/userInfo';
|
||||
import { useI18n } from 'vue-i18n';
|
||||
import { generateUUID } from '/@/utils/other';
|
||||
@@ -103,10 +105,11 @@ const loginFormRef = ref(); // 定义LoginForm表单引用
|
||||
const loading = ref(false); // 定义是否正在登录中
|
||||
const state = reactive({
|
||||
isShowPassword: false, // 是否显示密码
|
||||
passwordReadonly: true, // 密码输入框只读状态，用于防止浏览器自动填充
|
||||
ruleForm: {
|
||||
// 表单数据
|
||||
username: 'admin', // 用户名
|
||||
password: '123456', // 密码
|
||||
username: '', // 用户名
|
||||
password: '', // 密码
|
||||
code: '', // 验证码
|
||||
randomStr: 'blockPuzzle', // 验证码随机数
|
||||
},
|
||||
|
||||
@@ -37,14 +37,14 @@
|
||||
<expire v-if="loginType === LoginTypeEnum.EXPIRE" :username="username" @change="changeLoginType" />
|
||||
|
||||
<!-- 分割线 -->
|
||||
<div class="flex justify-center items-center my-6 space-x-3">
|
||||
<span class="w-20 h-[1.5px] bg-gray-200 dark:bg-slate-600"></span>
|
||||
<span class="text-gray-600 dark:text-slate-400">{{ $t('divider.or') }}</span>
|
||||
<span class="w-20 h-[1.5px] bg-gray-200 dark:bg-slate-600"></span>
|
||||
</div>
|
||||
<!-- <div class="flex justify-center items-center my-6 space-x-3">-->
|
||||
<!-- <span class="w-20 h-[1.5px] bg-gray-200 dark:bg-slate-600"></span>-->
|
||||
<!-- <span class="text-gray-600 dark:text-slate-400">{{ $t('divider.or') }}</span>-->
|
||||
<!-- <span class="w-20 h-[1.5px] bg-gray-200 dark:bg-slate-600"></span>-->
|
||||
<!-- </div>-->
|
||||
|
||||
<!-- 社交登录 -->
|
||||
<social @signInSuccess="signInSuccess" />
|
||||
<!-- <social @signInSuccess="signInSuccess" />-->
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user